Creating 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.

https://github.com/bunq/postman/

How it all hangs together

The installation call is the only call you can make with without any authorization token.

Call	Needs in the header	Needs in the body	Returns
/installation	Nothing	The public key (generated by you) of your server	1. installation token 2. public key of the server
/device-server	The installation token	the API key of your user and you server IP that will have access to bunq's API	A device ID
/session-server	Installation token	the API key of your user	Session token and user object

What's next

In the following pages you'll have a closer look on how to create your API Context by calling each of the 3 endpoints we explained here.