Chapter 0 setting up the API context

When integrating with the bunq API, security is a top priority. Instead of relying solely on API keys, bunq uses a three-step authentication process:

• installation,

• device registration,

• session creation

to ensure secure and controlled access. This approach prevents unauthorized use, protects sensitive financial data, and aligns with banking security standards like PSD2. Here’s how each step enhances security while keeping API access flexible and manageable.

Pro Tip: Simplify with Postman Using our Postman examples makes API integration super easy. We've pre-filled all the requests with environment variables, streamlining the process and reducing the risk of errors. It's by far the quickest way to get a live session, to play around with until you fully commit to a integration in your own application.This setup allows you to focus more on development and less on configuration, ensuring a smoother experience

Check it out here : Postman

Setting up the API context

We documented the API context in the following pages

• Creating the Installation

• Device Registration

• Start a Session

Host URL for the API endpoints

One change for partners, compared to regular API users is the base URL. Make sure to target

• Sandbox: https://partner-api.sandbox.bunq.com

• Production: https://api.partner.bunq.com