bunq API
- URL
-
https://api.bunq.com/v1 - Docs
- https://doc.bunq.com/
X-Bunq-Client-Authentication: <credential> Create an API key in bunq Developer or in the bunq app under Profile → Security & Settings → Developers → API keys. For sandbox testing, start with bunq Developer. After minting the key, you must activate it by creating an API context: call POST /installation, then POST /device-server, then POST /session-server as described in API Context, Device, Installation and Session.
X-Bunq-Client-Authentication: <credential> First create a client in bunq Developer Portal, then run the OAuth authorization-code flow from OAuth: redirect the user to https://oauth.bunq.com/auth, receive the authorization code, and exchange it at https://api.oauth.bunq.com/v1/token. bunq states the resulting access_token is then used “as a normal API Key” to open a session and call the API.
If you are a PSD2-certified third-party provider, integrate directly with the bunq Public API using your eIDAS certificate as described in Are you a Third Party Provider (TPP)? Start here! and Register as a TPP. bunq says PSD2 providers do not use the Developers Portal and instead register and authenticate entirely through API calls, beginning with POST /installation, POST /payment-service-provider-credential, POST /device-server, and POST /session-server.