Community OpenAPI document · agent-readyFinanceBankingapiKey421 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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.
Use for: I need to send a payment from my bunq account, Create a bunq.me payment request to share, Schedule a recurring monthly payment, List recent transactions on my bunq monetary account
Not supported: Does not handle non-bunq bank accounts, card processing for non-bunq merchants, or general accounting - use for bunq-account banking operations only.
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.
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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbunq.com%2Fbunq" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbunq.com%2Fbunq" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Create bunq.me tabs and fundraiser profiles for collecting payments
Run currency conversions and request foreign-exchange quotes
Manage installations, device-servers, and session-servers in bunq's auth flow
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
Register a new bunq installation
POST
/device-server
Register a device-server for an installation
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
Register a new bunq installation
POST
/device-server
Register a device-server for an installation
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
B
bunq API
- Non-Ready (F)27/100
25
Foundational Compliance63
Developer Experience & Jentic Compatibility12
AI-Readiness & Agent Experience42
Agent Usability100
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
25
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: FSignals: 4
0%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
12
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
47%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
42
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: D-Signals: 1
42%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the bunq API by hand means running its installation, device-server, and session-server handshake against api.bunq.com/v1, choosing the sandbox or production host, and signing each request yourself. Through Jentic you install once, import the bunq API from the API Directory, store the key once, and your agent calls it.
Permission scoping
bunq establishes access through a session handshake and references a session by id only when deleting it, so scope the agent by the operations it needs, such as reading the user or uploading an attachment. Because you choose the allowed operations, it can read account data without being able to delete a session unless you add that.
Credential isolation
Your bunq API key and installation and device-server material are stored once, encrypted, by your own Jentic One instance, and only a scoped, short-lived session token is injected at execution time. The long-lived secrets never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'read the bunq user' or 'upload an attachment', and Jentic returns the matching bunq operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe API
Stripe is a payment processor rather than a bank, with a different mental model for charges and customers.
Pick Stripe when accepting card payments online; bunq targets banking workflows on existing bunq accounts.
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 your Jentic One instance.
Can I limit what my agent is allowed to do with the bunq API?
Yes. Jentic One is self-hosted, so your own rules decide which bunq operations and credentials the agent may use. You can grant only the calls it needs, such as reading the user profile or uploading a public attachment, so it reads account data without being able to end a session unless you add that operation. Your bunq key and installation and device-server material stay in your own instance, and only a scoped, short-lived session token is injected per call.
GET STARTED