Hey bunqers 🌈, 

We're stopping the maintenance of the official bunq SDKs. While these libraries helped many developers get started, we’ve seen that the vast majority of developers integrate directly with the bunq API rather than through the SDKs.

As a result, our efforts naturally shifted toward improving the API itself and its documentation to accelerate improvements and better support the majority of developers building on our platform.

Why are we ending the maintenance of bunq SDKs? 

Maintaining SDKs across multiple languages requires significant ongoing effort. Instead of splitting our focus, we're investing that time into making the bunq API itself, and its documentation, even better. 

Our priority is ensuring that doc.bunq.com clearly explains every endpoint, flow, and concept so developers can easily write integrations directly from the source of truth, all in your favorite programming language. 

What will happen to my current project that uses the SDK?

If you're currently using one of the bunq SDKs, nothing will immediately change. The SDKs will remain available and we are not planning to remove them or disable their functionality in the near future. However, they will no longer receive updates, bug fixes, or improvements from our side. 

To make this clear, we’ve added a warning header to API responses when requests originate from an SDK. Over time, this means the SDKs may fall behind as the API evolves, which could lead to compatibility issues or missing support for new features. The source code for all SDKs will remain publicly available, so developers who wish to continue using them are free to fork the repositories and maintain or patch their own versions going forward.

How can I get started?

If you want to start exploring the bunq API we suggest you start by exploring our Postman Collection to get a intuition for what is possible and then taking a look at the Tutorial: My First Payment.