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

Bendigo and Adelaide Bank Banking Account Scheduled Payments API

Banking Account Scheduled Payment endpoints

Bendigo and Adelaide Bank Banking Account Scheduled Payments API is one of 14 APIs that Bendigo and Adelaide Bank publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Banking Account Scheduled Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and an AsyncAPI specification.

This API exposes 5 operations across 4 paths, and defines 39 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.

5 operations 4 paths 39 schemas 4 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Paths & Operations 5

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

Banking Account Scheduled Payments 5

Banking Account Scheduled Payment endpoints

GET
/banking/accounts/{accountId}/payments/scheduled
Get Scheduled Payments for Account
listScheduledPayments 9 params → 200400404406422
GET
/banking/payments/scheduled
Get Scheduled Payments Bulk
listScheduledPaymentsBulk 11 params → 200400406422
POST
/banking/payments/scheduled
Get Scheduled Payments For Specific Accounts
listScheduledPaymentsSpecificAccounts 8 params body → 200400406422
GET
/banking/accounts/{accountId}/payments/plans
Get Instalment Plans for Account
listInstalmentPlans 10 params → 200400404406422
GET
/banking/accounts/payments/plans
Get Instalment Plans Bulk
listInstalmentPlansBulk 9 params → 200400406422

Schemas 39

The contract defines 39 schemas that model the data the API accepts and returns. The most detailed are BankingInstalmentPlan (14 properties), BankingScheduledPaymentToV2 (9 properties), BankingInternationalPayee_bankDetails (9 properties), BankingScheduledPaymentV2 (8 properties). Each schema is shown below with its type and property counts.

BankingDigitalWalletPayee
object
4 properties 4 required
ErrorV2_meta
object
Additional data for customised error codes.
1 property
ResponseBankingInstalmentPlanList_data
object
1 property 1 required
BankingScheduledPaymentV2
object
8 properties 6 required
RequestAccountIdListV1_data
object
1 property 1 required
BankingInternationalPayee_bankDetails
object
9 properties 2 required
BankingInternationalPayee_bankDetails_bankAddress
object
2 properties 2 required
BankingPayeeId
string
A unique identifier for a Banking payee, generated according to [CDR ID Permanence](id-permanence) requirements.
BankingDomesticPayeeCard
object
1 property 1 required
BankingScheduledPaymentToV2
object
Object containing details of the destination of the payment. Used to specify a variety of payment destination types.
9 properties 1 required
BankingScheduledPaymentId
string
A unique identifier for a Banking scheduled payment, generated according to [CDR ID Permanence](id-permanence) requirements.
ResponseBankingScheduledPaymentsListV2_data
object
1 property 1 required
BankingScheduledPaymentRecurrenceOnceOff
object
Indicates that the payment is a once off payment on a specific future date. Mandatory if the recurrenceUType value is onceOff.
1 property 1 required
ResponseErrorListV2
object
1 property 1 required
BankingScheduledPaymentRecurrenceEventBased
object
Indicates that the schedule of payments is defined according to an external event that cannot be predetermined. Mandatory if the recurrenceUType value is event…
1 property 1 required
BankingInstalmentPlanSchedule
object
3 properties 2 required
BankingProductCategoryV2
string
The category to which a product or account belongs. See [here](product-categories) for more details.
ResponseBankingInstalmentPlanList
object
3 properties 3 required
LinksPaginated
object
5 properties 1 required
BankingScheduledPaymentFrom
object
Object containing details of the source of the payment. Currently only specifies an accountId but provided as an object to facilitate future extensibility and…
1 property 1 required
BankingScheduledPaymentSetV2
object
The set of payment amounts and destination accounts for this payment accommodating multi-part payments. A single entry indicates a simple payment with one dest…
4 properties 1 required
BankingScheduledPaymentRecurrenceIntervalSchedule
object
Indicates that the schedule of payments is defined by a series of intervals. Mandatory if the recurrenceUType value is intervalSchedule.
4 properties 1 required
Meta
object
BankingScheduledPaymentRecurrenceLastWeekday
object
Indicates that the schedule of payments is defined according to the last occurrence of a specific weekday in an interval. Mandatory if the recurrenceUType valu…
5 properties 2 required
BankingScheduledPaymentInterval
object
2 properties 1 required
BankingDomesticPayeeAccount
object
3 properties 2 required
MetaPaginated
object
2 properties 2 required
BankingScheduledPaymentRecurrence
object
Object containing the detail of the schedule for the payment.
6 properties 1 required
BankingBillerPayee
object
3 properties 2 required
BankingInternationalPayee_beneficiaryDetails
object
3 properties 1 required
BankingAccountId
string
A unique identifier for a Banking account, generated according to [CDR ID Permanence](id-permanence) requirements.
BankingDomesticPayeePayId
object
3 properties 2 required
BankingDomesticPayee
object
4 properties 1 required
BankingInstalmentPlan
object
14 properties 10 required
ResponseBankingScheduledPaymentsListV2
object
3 properties 3 required
BankingInternationalPayee
object
2 properties 2 required
RequestAccountIdListV1
object
2 properties 1 required
ErrorV2
object
4 properties 3 required
BankingInstalmentPlanId
string
A unique identifier for a Banking instalment plan, generated according to [CDR ID Permanence](id-permanence) requirements.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bendigo-and-adelaide-bank-banking-account-scheduled-payments-api-openapi.yml Raw ↑

Other APIs Bendigo and Adelaide Bank publishes across the network.

Bendigo and Adelaide Bank Accounts API
Bendigo and Adelaide Bank Attachments API
Bendigo and Adelaide Bank Banking Account Balances API
Bendigo and Adelaide Bank Banking Account Direct Debits API
Bendigo and Adelaide Bank Banking Account Transactions API
Bendigo and Adelaide Bank Banking Accounts API
Bendigo and Adelaide Bank Banking Payees API
Bendigo and Adelaide Bank Banking Products API
Bendigo and Adelaide Bank Categories API
Bendigo and Adelaide Bank Tags API
Bendigo and Adelaide Bank Transactions API
Bendigo and Adelaide Bank Utility endpoints API
Where this information came from

This is an independent, third-party profile of Bendigo and Adelaide Bank Banking Account Scheduled Payments 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.