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 Utility endpoints API

Some endpoints exist not to expose data, but to test the APIitself. Currently there is only one endpoint in this group: ping!

Bendigo and Adelaide Bank Utility endpoints 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 Utility endpoints. 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 1 operation across 1 path, and defines 3 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.

1 operations 1 paths 3 schemas 1 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://api.cdr.bendigobank.com.au/cds-au/v1/banking/products
Resource Areas
1

Paths & Operations 1

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

Utility endpoints 1

Some endpoints exist not to expose data, but to test the API itself. Currently there is only one endpoint in this group: ping!

GET
/util/ping
Ping
→ 200401

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are ErrorObject (4 properties), ErrorResponse (1 property), PingResponse (1 property). Each schema is shown below with its type and property counts.

ErrorObject
object
Provides information about an error processing a request.
4 properties 3 required
PingResponse
object
Basic ping response to verify authentication.
1 property 1 required
ErrorResponse
object
Generic error response that returns one or more errors.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bendigo-and-adelaide-bank-utility-endpoints-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 Scheduled Payments 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
Where this information came from

This is an independent, third-party profile of Bendigo and Adelaide Bank Utility endpoints 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.