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

BCU Bank Banking Payees API

Banking Payee endpoints

BCU Bank Banking Payees API is one of 7 APIs that BCU Bank publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 2 operations across 2 paths, and defines 18 schemas. It is described by OpenAPI 3.0.3, at version 1.36.0.

Requests are made against a single base URL, https://mtls.dh.example.com/cds-au/v1.

2 operations 2 paths 18 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.36.0
Base URL
https://public.cdr-api.bcu.com.au/cds-au/v1/banking/products
Resource Areas
1

Paths & Operations 2

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

Banking Payees 2

Banking Payee endpoints

GET
/banking/payees
Get Payees
listBankingPayees 9 params → 200400406422
GET
/banking/payees/{payeeId}
Get Payee Detail
getBankingPayeeDetail 7 params → 200400404406422

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are LinksPaginated (5 properties), BankingPayeeV2 (5 properties), ErrorV2 (4 properties), BankingDomesticPayee (4 properties). Each schema is shown below with its type and property counts.

BankingPayeeV2
object
5 properties 3 required
Meta
object
Links
object
1 property 1 required
BankingPayeeDetailV2
ResponseBankingPayeeByIdV2
object
3 properties 2 required
BankingDomesticPayeePayId
object
3 properties 2 required
LinksPaginated
object
5 properties 1 required
ErrorV2
object
4 properties 3 required
ResponseBankingPayeeListV2
object
3 properties 3 required
BankingDomesticPayeeAccount
object
3 properties 2 required
BankingDomesticPayee
object
4 properties 1 required
BankingBillerPayee
object
3 properties 2 required
BankingDigitalWalletPayee
object
4 properties 4 required
MetaPaginated
object
2 properties 2 required
BankingPayeeId
string
A unique identifier for a Banking payee, generated according to [CDR ID Permanence](id-permanence) requirements.
ResponseErrorListV2
object
1 property 1 required
BankingInternationalPayee
object
2 properties 2 required
BankingDomesticPayeeCard
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bcu-bank-banking-payees-api-openapi.yml Raw ↑

Other APIs BCU Bank publishes across the network.

BCU Bank Banking Account Balances API
BCU Bank Banking Account Direct Debits API
BCU Bank Banking Account Scheduled Payments API
BCU Bank Banking Account Transactions API
BCU Bank Banking Accounts API
BCU Bank Banking Products API
Where this information came from

This is an independent, third-party profile of BCU Bank Banking Payees 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.