Cheerfy · Authentication Profile

Cheerfy Authentication

Authentication

Cheerfy secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyRestaurantHospitalityCRMLoyaltyCustomer EngagementMarketing AutomationOnline OrderingPayments
Methods: http Schemes: 1 OAuth flows: API key in: header

Security Schemes

TokenAuth http
scheme: Token · in: header ()

Source

Authentication Profile

cheerfy-authentication.yml Raw ↑
generated: '2026-08-10'
method: probed
source: live HTTP probe of https://webhook.cheerfy.com/
note: >-
  There is no OpenAPI to derive securitySchemes from, and the Loyalty Card / Coupons API reference
  pages on docs.cheerfy.com are unreadable to a non-JavaScript client. This profile records what a
  live probe of the one reachable Cheerfy API host actually returned: an HTTP 401 carrying
  "WWW-Authenticate: Token", the Django REST Framework token-authentication challenge. The scheme
  name, header form and error envelope below are observed, not inferred from documentation.
summary:
  types: [http]
  api_key_in: [header]
  oauth2_flows: []
  openid_connect: false
  mutual_tls: false
schemes:
- name: TokenAuth
  type: http
  scheme: Token
  in: header
  parameter_name: Authorization
  form: 'Authorization: Token <key>'
  host: https://webhook.cheerfy.com
  sources: [probe]
  evidence:
    url: https://webhook.cheerfy.com/
    http_status: 401
    www_authenticate: Token
    body: '{"detail":"Authentication credentials were not provided."}'
    server: gunicorn
    framework: Django REST Framework (inferred from the challenge + error envelope shape)
    fetched: '2026-08-10'
oauth:
  published: false
  discovery:
    openid_configuration: not served (404/503/307 on every Cheerfy host)
    oauth_authorization_server: not served (404/503/307 on every Cheerfy host)
  note: >-
    auth.cheerfy.com is referenced by the admin console at admin.cheerfy.com/login/ but returns 404
    on / and on both OAuth/OIDC discovery paths, so no authorization-server metadata is public.
key_issuance:
  self_service: false
  note: >-
    No public sign-up for API credentials. Credentials are issued inside the tenant admin console
    (https://admin.cheerfy.com/login/); the business-services terms state only that "CHEERFY
    provides an API to allow the Business to engage third party service providers".
gaps:
- no machine-readable specification declaring securitySchemes
- no public authentication reference page a machine can read
- no OAuth or OIDC discovery document on any host

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/cheerfy-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.