Cognito · Authentication Profile

Cognito Authentication

Authentication

Cognito authenticates every API request with HTTP request signatures (the Cavage "Signing HTTP Messages" draft), not a bearer token or HTTP Basic. Each request carries a Date header, a Digest header (base64 SHA-256 of the body), and an Authorization: Signature header whose signature is an HMAC-SHA256 over the "(request-target) date digest" signing string, keyed with the API secret. The API key (keyId) identifies the organization; the API secret is used only server-side to compute the signature and is never transmitted.

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

CompanyIdentityIdentity VerificationKYCAMLComplianceFraud PreventionOnboardingWatchlist ScreeningKnow Your Customer
Methods: httpSignature Schemes: 1 OAuth flows: API key in: header

Security Schemes

HTTPSignature http
scheme: signature

Source

Authentication Profile

cognito-authentication.yml Raw ↑
generated: '2026-07-18'
method: searched
source: https://cognitohq.com/docs/guides/authenticating
docs: https://cognitohq.com/docs/guides/authenticating
description: >-
  Cognito authenticates every API request with HTTP request signatures (the
  Cavage "Signing HTTP Messages" draft), not a bearer token or HTTP Basic. Each
  request carries a Date header, a Digest header (base64 SHA-256 of the body),
  and an Authorization: Signature header whose signature is an HMAC-SHA256 over
  the "(request-target) date digest" signing string, keyed with the API secret.
  The API key (keyId) identifies the organization; the API secret is used only
  server-side to compute the signature and is never transmitted.
summary:
  types: [httpSignature]
  api_key_in: [header]
  oauth2_flows: []
schemes:
- name: HTTPSignature
  type: http
  scheme: signature
  algorithm: hmac-sha256
  key_id: API key (keyId)
  secret: API secret (HMAC key, never transmitted)
  signed_headers:
  - (request-target)
  - date
  - digest
  headers:
    Date: W3C/RFC 1123 timestamp, e.g. "Thu, 25 Aug 2016 22:37:14 GMT"
    Digest: "SHA-256=<base64(sha256(body))>"
    Authorization: >-
      Signature keyId="<api-key>",algorithm="hmac-sha256",headers="(request-target)
      date digest",signature="<base64 hmac-sha256 signature>"
  clock_skew: Date must be within 15 minutes of server time (per webhook verification docs)
  sources: [docs]
notes: >-
  Community and beta SDKs implement the signing so integrators do not compute the
  HMAC by hand. No OpenAPI spec was located to derive from; profile captured from
  the published authentication guide.

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/cognito-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.