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

bunq Payment API

Execute and read payments (including SEPA) for a monetary account.

bunq Payment API is one of 9 APIs that bunq publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 5 operations across 3 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against 2 base URLs: https://api.bunq.com/v1, https://public-api.sandbox.bunq.com/v1.

5 operations 3 paths 5 schemas 3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.bunq.com/v1
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

bunq Payment API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Bunq-Client-Authentication (sessionToken). An API key is passed in the header as X-Bunq-Client-Authentication (installationToken). By default, every request must be authenticated.

  • sessionToken — Session token obtained from POST /session-server, sent on every business call. In addition, each request body must be signed with your private key and the sign…
  • installationToken — Installation token from POST /installation, used only for the device-server and session-server handshake calls.

Paths & Operations 5

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

Payment 5

Execute and read payments (including SEPA) for a monetary account.

GET
/user/{userID}/monetary-account/{monetaryAccountID}/payment
List payments
listPayments 5 params → 200401
POST
/user/{userID}/monetary-account/{monetaryAccountID}/payment
Create a payment
createPayment 2 params body → 200400401
GET
/user/{userID}/monetary-account/{monetaryAccountID}/payment/{paymentID}
Get a payment
getPayment 3 params → 200401404
GET
/user/{userID}/monetary-account/{monetaryAccountID}/draft-payment
List draft payments
listDraftPayments 2 params → 200401
POST
/user/{userID}/monetary-account/{monetaryAccountID}/draft-payment
Create a draft payment
createDraftPayment 2 params body → 200400

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Pointer (3 properties), PaymentInput (3 properties), Amount (2 properties), Response (1 property). Each schema is shown below with its type and property counts.

ErrorResponse
object
bunq error envelope.
1 property
Amount
object
2 properties 2 required
PaymentInput
object
3 properties 3 required
Pointer
object
A bunq alias ("pointer") identifying a counterparty.
3 properties 2 required
Response
object
Generic bunq response envelope. Every bunq response wraps its payload in a top-level Response array whose items are single-key objects keyed by the resource ty…
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bunq-payment-api-openapi.yml Raw ↑

Other APIs bunq publishes across the network.

bunq Attachment API
bunq Card API
bunq Customer Statement API
bunq Handshake API
bunq Monetary Account API
bunq Notification Filter API
bunq Request Inquiry API
bunq User API
Where this information came from

This is an independent, third-party profile of bunq Payment 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.