Azupay · Authentication Profile

Azupay Authentication

Authentication

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

PaymentsAustraliaReal-Time PaymentsAccount-to-AccountNew Payments PlatformPayIDPayToMoney TransferConfirmation of PayeeOpen Banking
Methods: apiKey, oauth2 Schemes: 3 OAuth flows: clientCredentials API key in: header

Security Schemes

SecretKey apiKey
· in: header (Authorization)
DistributableKey apiKey
· in: header (Authorization)
OAuth2ClientCredentials oauth2

Source

Authentication Profile

Raw ↑
generated: '2026-07-24'
method: searched
source: openapi/azupay-check-accounts.yml, openapi/azupay-configuration.yml, openapi/azupay-payment-agreement.yml,
  openapi/azupay-payment-request.yml, openapi/azupay-payment.yml, openapi/azupay-reports.yml
docs: https://developer.azupay.com.au/docs/getting-started-1, https://developer.azupay.com.au/docs/oauth-20-api
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - clientCredentials
schemes:
- name: SecretKey
  type: apiKey
  in: header
  parameter: Authorization
  description: Secret (SECR) key for restricted/charging operations (including outbound payments); store
    encrypted, restrict to authorised systems.
  sources: &id001
  - openapi/azupay-check-accounts.yml
  - openapi/azupay-configuration.yml
  - openapi/azupay-payment-agreement.yml
  - openapi/azupay-payment-request.yml
  - openapi/azupay-payment.yml
  - openapi/azupay-reports.yml
- name: DistributableKey
  type: apiKey
  in: header
  parameter: Authorization
  description: Distributable (DIST) key with limited access; may be exposed publicly to payers.
  sources: *id001
- name: OAuth2ClientCredentials
  type: oauth2
  flow: clientCredentials
  description: 'Additional server-to-server option (enabled per client). Short-lived JWT bearer token;
    oauth2TokenUrl and allowed scopes are returned by enableClientOAuth2/getClientOAuth2. Send as Authorization:
    Bearer <token>.'
  tokenUrl: dynamic (oauth2TokenUrl)
  sources:
  - 'docs: https://developer.azupay.com.au/docs/oauth-20-api'

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/azupay-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 email required.

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