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 Webhooks API

Webhooks provide a mechanism for a configured URL to receiveevents when transaction activity occurs on Up. You can think ofwebhooks as being like push notifications for your server-sideapplication.

Bendigo and Adelaide Bank Webhooks 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 Webhook. 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 6 operations across 4 paths, and defines 12 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.

6 operations 4 paths 12 schemas 1 DELETE3 GET2 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 6

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

Webhooks 6

Webhooks provide a mechanism for a configured URL to receive events when transaction activity occurs on Up. You can think of webhooks as being like push notifications for your ser…

GET
/webhooks
List webhooks
1 param → 200
POST
/webhooks
Create webhook
body → 201
GET
/webhooks/{id}
Retrieve webhook
1 param → 200
DELETE
/webhooks/{id}
Delete webhook
1 param → 204
POST
/webhooks/{webhookId}/ping
Ping webhook
1 param → 201
GET
/webhooks/{webhookId}/logs
List webhook logs
2 params → 200

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are WebhookResource (5 properties), WebhookEventResource (4 properties), WebhookDeliveryLogResource (4 properties), ListWebhooksResponse (2 properties). Each schema is shown below with its type and property counts.

ListWebhooksResponse
object
Successful response to get all webhooks. This returns a paginated list of webhooks, which can be scrolled by following the prev and next links if present.
2 properties 2 required
WebhookResource
object
Provides information about a webhook.
5 properties 4 required
CreateWebhookRequest
object
Request to create a new webhook. This currently only requires a url attribute.
1 property 1 required
WebhookDeliveryStatusEnum
Specifies the nature of the success or failure of a webhook delivery attempt to the subscribed webhook URL. The currently returned values are described below:…
GetWebhookResponse
object
Successful response to get a single webhook.
1 property 1 required
WebhookInputResource
object
Represents a webhook specified as request input.
1 property 1 required
CreateWebhookResponse
object
Successful response after creating a webhook.
1 property 1 required
ListWebhookDeliveryLogsResponse
object
Successful response to get all delivery logs for a webhook. This returns a paginated list of delivery logs, which can be scrolled by following the next and pre…
2 properties 2 required
WebhookDeliveryLogResource
object
Provides historical webhook event delivery information for analysis and debugging purposes.
4 properties 4 required
WebhookEventCallback
object
Asynchronous callback request used for webhook event delivery.
1 property 1 required
WebhookEventResource
object
Provides the event data used in asynchronous webhook event callbacks to subscribed endpoints. Webhooks events have defined eventTypes and may optionally relate…
4 properties 4 required
WebhookEventTypeEnum
Specifies the type of a webhook event. This can be used to determine what action to take in response to the event, such as which relationships to expect.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bendigo-and-adelaide-bank-webhooks-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 Webhooks 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.