How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Azupay Payment API

This API allows you to make outbound payments to PayID or NPP enabled BSB accounts.

Azupay Payment API is one of 10 APIs that Azupay publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payment. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 2 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against 2 base URLs: https://api-uat.azupay.com.au/v1, https://api.azupay.com.au/v1.

3 operations 2 paths 7 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.azupay.com.au/v1
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Azupay Payment API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (SecretKey). An API key is passed in the header as Authorization (DistributableKey).

  • SecretKey — The secret key is used to access restricted functions and should be stored securely in your system. It is required for operations which may result in additiona…
  • DistributableKey — The distributable key has limited access and may be exposed publicly to your payers.

Paths & Operations 3

Across 2 paths, the API surfaces 3 operations — 1 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Payment 3

This API allows you to make outbound payments to PayID or NPP enabled BSB accounts.

GET
/payment
Get a Payment.
getPayment 1 param → 200400401404
POST
/payment
Make a Payment.
makePayment body → 201400401409
POST
/payment/search
Search for Payments.
searchPayment 2 params body → 200400401

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are ErrorModel (2 properties), PaymentObj (1 property), PaymentStatusObj (1 property), PaymentSearchObj (1 property). Each schema is shown below with its type and property counts.

fromDateUTC
string
The report date in ISO date/time string format in UTC
PaymentSearchObj
object
1 property
toDateUTC
string
The report date in ISO date/time string format in UTC
PaymentStatusObj
object
1 property 1 required
PaymentObj
object
1 property 1 required
ErrorModel
object
2 properties 1 required
PaymentSearchResponseObj
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

azupay-payment-api-openapi.yml Raw ↑

Other APIs Azupay publishes across the network.

Azupay API Keys API
Azupay Billing and Transaction Reports API
Azupay Check Accounts API
Azupay Clients API
Azupay Current Balances API
Azupay Payment Agreement API
Azupay Payment Agreement Request API
Azupay Payment Initiation API
Azupay Payment Request API
Where this information came from

This is an independent, third-party profile of Azupay Payment API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.