bunq API

Name: bunq API
Brand: bunq API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingapiKey421 EndpointsREST

For Agents

Move money between bunq monetary accounts, send and request payments, manage cards and scheduled payments, and read transaction history on a bunq user's behalf.

Install Jentic One Beta

Connect the bunq API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the bunq API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with bunq API.

Create and read bunq monetary-account-bank accounts and balances

Initiate single payments and request-inquiry payment requests

Schedule recurring payments via the scheduled-payment endpoints

Issue and manage debit, credit, and card-batch operations

GET STARTED

Start building with bunq API

Explore with Jentic

View OpenAPI Document

The bunq API is the public banking API for bunq, a European mobile bank, covering monetary accounts, payments, scheduled payments, cards, attachments, bunq.me payment requests, currency conversion, and a large surface of user, device, and session management endpoints. It supports both a sandbox environment at public-api.sandbox.bunq.com and the production environment at api.bunq.com. Authentication uses bunq's installation-and-session model — register an installation, register a device-server, then create a session to obtain a session token used for API calls.

Use Cases

Patterns agents use bunq API for, with concrete tasks.

★ Send and receive payments programmatically

Initiate outbound payments from a bunq monetary account and create inbound bunq.me payment requests or tabs for customers. Supports both single and scheduled payments, with status visible through the related read endpoints. Suitable for European businesses already on bunq that want to script reconciliation or payouts without manual taps in the bunq app.

POST a payment under /user-{userType}/{userID}/monetary-account/{accountID}/payment with amount and counterparty alias, then read it back to confirm status.

Card issuance and management

Create and manage bunq debit and credit cards, including batch operations and card-name updates. Useful for fintech use cases that issue physical or virtual cards on top of bunq accounts and need to control card status without operator intervention.

Issue a virtual debit card through the card-debit endpoints, then update its name with the card-name resource so the holder sees the correct label.

Currency conversion and FX

Quote and execute currency conversions between bunq monetary accounts denominated in different currencies. The currency-conversion and currency-cloud-payment-quote endpoints expose quote retrieval and execution, suitable for treasury workflows that move balances across EUR, USD, and other supported currencies.

Request a currency-cloud-payment-quote, present the rate, then execute a conversion between the EUR and USD bunq monetary accounts on the user's behalf.

AI agent personal banking via Jentic

An AI assistant can read a bunq user's recent transactions, prepare a payment, and confirm with the user before sending — all without the agent ever holding the bunq session token directly. Jentic isolates the bunq installation, device-server, and session-server credentials and issues scoped, short-lived access for each call.

Search Jentic for 'send a bunq payment', load the payment schema, and execute after the user confirms the recipient, amount, and currency.

Key Endpoints

421 endpoints — the bunq api is the public banking api for bunq, a european mobile bank, covering monetary accounts, payments, scheduled payments, cards, attachments, bunq.

METHOD

PATH

DESCRIPTION

POST

/installation

POST

/device-server

POST

/session-server

Create a session and obtain a session token

GET

/user

List bunq users associated with the session

POST

/attachment-public

Upload a public attachment

POST

/avatar

Create an avatar from an uploaded attachment

DELETE

/session/{itemId}

End an active bunq session

POST

/installation

POST

/device-server

POST

/session-server

Create a session and obtain a session token

GET

/user

List bunq users associated with the session

POST

/attachment-public

Upload a public attachment

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The bunq API key, installation, and device-server material stay encrypted in the Jentic vault. Agents receive scoped, short-lived session tokens per operation — bunq's long-lived secrets never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'send a bunq payment') and Jentic returns the matching payment or scheduled-payment operation with its full request schema, so the agent picks the right endpoint without reading bunq's developer portal.

Time to first call

Direct bunq integration: 3-7 days, mostly spent on the installation and device-server flow. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using bunq API through Jentic.

What authentication does the bunq API use?

bunq uses an installation-and-session model: register an installation, register a device-server with your API key, then create a session-server to obtain a session token used in subsequent calls. Through Jentic, the long-lived API key and installation/device material stay vaulted while the agent uses scoped, short-lived session credentials per operation.

Can I send a payment programmatically through the bunq API?

Yes. After establishing a session, POST a payment under the user's monetary-account path with amount, currency, and counterparty alias. The response includes the payment ID, which you can read back to verify status.

Does bunq support scheduled and recurring payments?

Yes — the scheduled-payment endpoints create, read, update, and delete recurring payments tied to a monetary account, making it suitable for subscriptions, rent, or any recurring outflow.

How do I run currency conversion between bunq accounts?

Use the currency-conversion and currency-cloud-payment-quote resources to retrieve a quote and then execute the conversion between two bunq monetary accounts in different currencies. Quotes are time-limited; execute promptly after retrieval.

What are the rate limits for the bunq API?

The OpenAPI spec does not declare explicit limits. bunq publishes per-application throttle guidance in their developer documentation — handle 429 responses with backoff and reuse session tokens until they expire to minimise authentication overhead.

How do I send a bunq payment through Jentic?

Run `pip install jentic` and search for 'send a bunq payment'. Jentic returns the matching payment operation under the user/monetary-account path, you load the schema, and execute with the recipient and amount — installation/session credentials stay in the Jentic vault.

bunq API

Connect the bunq API to your agent

Capabilities

Start building with bunq API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs