Skip to content

Status of the API in 2023 #150

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
Ditscheridou opened this issue Aug 1, 2023 · 3 comments
Closed

Status of the API in 2023 #150

Ditscheridou opened this issue Aug 1, 2023 · 3 comments

Comments

@Ditscheridou
Copy link

Hello,

this API is not maintained since 2020, @angelomelonas seems to left the company. I would really wish that you guys communicate in a better and do not promote this api as much as you do, because it's not working. Can you please give us some insights how the roadmap currently looks like?

@pputerla
Copy link

pputerla commented Aug 4, 2023

Java sdk doesn't even compile (#148)
I have confirmed that with the current code (master, recent tags, develop) - there's a lot of missing code (classess).

@two-trick-pony-NL
Copy link
Member

two-trick-pony-NL commented Mar 5, 2025

👋 Hey @Ditscheridou and @pputerla

I work at bunq and am currently reviewing the bunq API docs, open issues and SDK’s and came across your issue. I know it’s been open for a while, and I’d love to understand how it’s impacting you. Beyond the obvious -fixing this issue-, what else could we do to improve your experience with our API?

If you want to share your thoughts on how we can improve on our public API:

📅 I'd love to schedule a 15 minute interview to understand your needs through: Calendly
💬 Or if you don't have time for a call, you can give us some general feedback through this form

Your feedback will go straight to our product team! 🚀

@two-trick-pony-NL
Copy link
Member

Hi! We're closing this issue as it's tied to an older version of our SDKs, and we've since completely revamped them as part of bunq Update 28.

This is a fresh start—we've tested the new SDKs extensively, and we’ll be putting them to the test again during our upcoming hackathon this Friday, where we’ll fix idiosyncrasies on the spot. (You’re welcome to join us!)

If this issue (or a new one) shows up with the updated SDKs, feel free to reopen or file a new report—we're happy to jump on it.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants