Back in the day when I was a bunq employee, I was, sort of, maintaining the bunq SDK's when time permitted me to do so. With this being said, I have some good knowledge on how it works etc.
As I've switched from PHP to Golang, (who uses PHP anyway :troll: ) there is no Golang SDK for the bunq api. At least, there was no "completed" one. So I've build one :D.
This particular version has been running for 3 moths now in my own personal project. So far so good, only annoying issue that there is:
1. you create a new bunq client
2. you're done with it so you close it
3. when you do, I delete the session (why should the session be left open anyway ?)
4. you quickly re-create a new bunq client (for whatever reason you might have)
5. 429 on the /session endpoint 😑
Other then that, there is a build in limit to execute requests to the same endpoint with a 1 sec delay to prevent bunq's annoying 429's to fire, so far I had 0 429 on other endpoints than /session so that's also Gucci.
Currently all the code for the endpoints are hand written instead of generated. Golangs templating system makes it super nice to generate code based of a template so maybe ill consider building one if there are a lot of users that will use this, if not its not worth it ofc and ill just keep adding endpoints by hand if needed. Its relatively easy to do.
There could be some unexpected code that needs to be exported, if you've find any or you're not sure, don't hesitate to ask 😊.