API documentation feedback

Jorn-Indigo-Falcon

I have 2 little feedback points:

Logging in with the test developers account first requires the pin code. This pincode is listed in the settings account and works fine. However, a second verification is then required. By default it asks for a passphrase. This one is unknown to me (it is not the pin code). I then tried the face recognition (just to try if it would magically work) and to my surprise this one did work. This piece of information would be really useful to add at the settings page where the test accounts are listed. When you want to verify the qr code at a later stage in the app, this same passphrase or face identication is required again, where the same steps need to be taken.The API documentation for https://doc.bunq.com/api/1/call/draft-share-invite-bank as well as https://doc.bunq.com/api/1/call/share-invite-bank-inquiry/method/list, is missing 3 rather important attributes for both the returned attribute explanation as example json. This goes for get, post, update and list.int id: the id of the shared-bank-invite

string created

string updated

Kevin-Violet-Zebra

Hey Jorn,

Nice to hear that you have been playing with the API💻.

Thanks for your feedback and suggestions :), I've written them down on our wish list 👍

Regarding the examples, it is possible that the actual response might be a little bit different then the examples shown on our documentation page.😉

Keep building great stuff 💪.

Shopforce

Hey Kevin

please have a look at https://github.com/bunq/sdk_php/issues/108

Did you guys process the suggestions by Jorn / topic starter? How can Jorn / the community track this? Will this topic then be closed?

Payment description conditions

Next the the amount of allowed characters, are there any conditions regarding special characters when POSTing a Payment?

Observations

the documentation does not mention them: https://doc.bunq.com/api/1/call/payment/method/postwhen using the Bunq App (Android) a Payment can be made between Bunq accounts with a description that involves a pipe | character, for example: HELLO | good-byewhen using the API a 400 Bad Request response is returned while using the same description

It might be an idea to:

have behaviour that is equal for all ways to create a Payment (App + API)improve the returned error messagedocument the requirements, is a regular expression involved? => name it in the documentation

Incorrect API request limits documented

The documentation at https://doc.bunq.com/api/1/page/errors as a section about the 429 too much request error:

Our rate limits per IP address per endpoint:

GET requests: 3 within any 3 consecutive secondsPOST requests: 5 within any 3 consecutive secondsPUT requests: 2 within any 3 consecutive seconds

This seems outdated when looking at errors like:

endpoint "device-server": Too many requests. You can do a maximum of 9 GET call per 9 second to this endpoint.endpoint "user" (to POST a Payment): Too many requests. You can do a maximum of 5 calls per 5 second to this endpoint.

Also see: https://together.bunq.com/topic/api-rate-limiting-does-not-function-in-accordance-with-documentation-and-is-too-low-to-be-usable

Please include the name of the endpoint in the error message instead of "this endpoint". Also note that for payment the method type (POST) is not mentioned.

We all appreciate Bunq offering an API, but please provide better documentation (for example: https://developer.moneybird.com/api, or the level of detail in https://stripe.com/docs/api) and a better mechanism to have the community provide feedback. The current approach, using "Together" is causing headaches, is simply to suitable for this task... Stripe has arrived in the Benelux and has been investing in Bunq competitor "Monzo" which probably integrates great with their payment solutions, so it makes great (operationald and strategic) sense for Bunq to improve the current situation. Just my 2 cents... Just open up a GitHub / BitBucket / GitLab repo for the documentation, pronto.