OPENAPI & POSTMAN

Bring the contract
into your own tools.

Download the published specification or collection, check the request schema and set up a private environment. Exports describe the API contract; they do not grant access or activate a product.

PUBLISHED EXPORTS

Choose your format.

Both exports come from the same documentation source as the API reference. Credentials are not included.

OPENAPI

OpenAPI specification

Inspect endpoint definitions and request schemas in your existing API tooling.

/Developers/Data.aspx?resource=openapi

POSTMAN

Postman collection

Review the published requests and configure your own approved environment.

/Developers/Data.aspx?resource=postman

BEFORE THE FIRST REQUEST

A few checks worth making.

01 / ENVIRONMENT

Use the approved base URL.

Get the environment and base URL from your authorised BankU contact. The public website address is not the API base URL.

02 / CREDENTIALS

Keep secrets private.

Store credentials in a private environment, outside source control. Do not include them in shared collections, screenshots or support messages.

03 / ACCESS

Confirm product access.

A published endpoint is not an activation approval. Confirm credentials, source-IP whitelisting and the required product entitlement before testing.

04 / VALIDATION

Test the failure paths too.

Check invalid inputs, timeouts and unsuccessful responses. Follow the endpoint's documented retry and idempotency rules.

Looking for one endpoint?

The API reference is organised by product. Use it to check the required fields, provider contract and examples before writing your request.

Browse the API reference →

Search documentation

↑ ↓ Results Tab Controls Enter Open