Assembly Payments · Authentication Profile

Assembly Payments Authentication

Authentication

Assembly Payments secures its APIs with http and oauth2 across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

CompanyPaymentsFintechMarketplacesDigital WalletsPayoutsAustraliaPayTo

Methods: http, oauth2 Schemes: 3 OAuth flows: clientCredentials API key in:

Security Schemes

oAuth2ClientCredentials oauth2

· flows: clientCredentials

basicAuth http

scheme: basic

bearerAuth http

scheme: bearer

Source

Authentication Profile

generated: '2026-10-22'
method: searched
source: https://developer.hellozai.com/reference/overview
summary:
  types:
  - http
  - oauth2
  oauth2_flows:
  - clientCredentials
schemes:
- name: oAuth2ClientCredentials
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://au-0000.sandbox.auth.assemblypay.com/tokens
    scopes: 0
  description: Please refer to Authentication section within https://developer.assemblypayments.com/reference#authentication
  sources:
  - openapi/assembly-payments-api-openapi.yml
  - openapi/assembly-payments-asynchronous-api-openapi.yml
  - openapi/assembly-payments-upcoming-initiate-last-domestic-leg-payout-api-openapi.yml
- name: basicAuth
  type: http
  scheme: basic
  sources:
  - openapi/assembly-payments-asynchronous-api-openapi.yml
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  sources:
  - openapi/assembly-payments-payto-api-openapi.yml
  - openapi/assembly-payments-supplementary-data-apis-api-openapi.yml
  - openapi/assembly-payments-webhooks-api-openapi.yml
docs: https://developer.hellozai.com/reference/overview
docs_pages:
- https://developer.hellozai.com/reference/overview
- https://developer.hellozai.com/reference/token
- https://developer.hellozai.com/docs/developer-checklist
token:
  flow: OAuth2 client credentials
  lifetime: tokens expire in 60 minutes
  issuers:
    prelive: https://au-0000.sandbox.auth.assemblypay.com
    live: https://au-0000.auth.assemblypay.com
  credentials: Client ID, Client Secret, and Scope revealed from the Dashboard Platform Profile menu
  header: 'Authorization: Bearer <token>'
frontend_tokens: Hosted Form / Hosted Fields require an expirable card token generated on the back-end (generateToken) so the API key is never exposed.

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/assembly-payments-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.

GitHub Google LinkedIn

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