API PRODUCTION and SANDBOX context creation issues

Deddo

Downloaded the BUNQ API yesterday (bash <(curl -s https://tinker.bunq.com/php/setup.sh) and installed it on CentOS 7, so for so good but when using my freshly generated API key I got two errors:

Issue 1: Sandbox
For Sandbox a (normal) authorisation error. Already contacted Bunq support and they referred me to the topic https://together.bunq.com/d/2859-sandbox-api-key_2, where I could find the answer (using the last i.e. yesterday downloaded API version) and was advised to open a new topic.

Issue 2: Production
I was referred by Bunq support to https://github.com/bunq/sdk_php/issues/7, a long closed topic which hints on upgrading to a newer curl version (which is not that easy for me to do, any hints on Centos 7/PHP 7.0/Curl 7.29.0 upgrading to a higher version fo cUrl apreciated). There was a quickfix in the post on commenting out line 163 in ApiClient.php. Thankfully this solved the production issue, so anybody encountering the same problem might use the same fix: commenting out now line 315 (CURLOPT_PINNEDPUBLICKEY), probably because the ApiClient.php changed between 2/8/2017 and yesterday), solved this issue. Also the location of ApiClient.php changed to vendor\bunq\sdk_php\Http\ApiClient.php. As the topic is closed and I spend a considerable amount of time trying to fix the error (three different servers/two different CentOS/PHP versions), maybe a suggestion to make this tempory fix a permanent one?

Just did a retest with the production fix on the sandbox problem, but no solution there, so help appreciated on the first issue.

Bastiaan

VSV Marketing Hi !

I only can reproduce your first issue when i have a typo in my Sandbox API-key.
Did your Sandbox API-key starts with sandbox_ and is 64 characters long?

Deddo

I am using the same API key (generated from the app) for sandbox and production (of 64 characters)

Bastiaan

VSV Marketing The production API-key is not working in the Sandbox environment.
You have to generate a Sandbox API-key, check this topic for more info:
https://together.bunq.com/d/2859-sandbox-api-key_2

Cheers!

Deddo

Just tested it with preceding the 64 characters with sandbox_ but same result (and using copy paste while the same tool for generating the production context with the 64 character key and the aforementioned quick-fix now works)

Deddo

Thanx Bastiaan, that was it. With the curl command in your post I was able to generate the 64 character key (including sandbox_) and that solved it

Deddo

Maybe include a section on the official API page doc.bunq.com on this difference in the two API keys or even better in the context creation code (eg a reminder) /vendor/bin/bunq-install?

Bastiaan

VSV Marketing You're right, the documentation is not very clear about how to generate the sandbox API-key (for example with the cUrl command).

Maybe you can report this via https://github.com/bunq/doc/issues ?

Deddo

Bastiaan Learning .... also using this support system now with a personal message to you (I think). Don't have a github profile yet put will put the 2 suggestions there too

Sander

VSV Marketing Doc recently got tweaked for Sandbox explanations; the steps are described in detail at https://doc.bunq.com/#android-emulator. This section is linked from the introduction of the doc as well. More improvements (either by opening issues/providing Pull Requests) are always welcome of course. 😁

Deddo

Maybe some room for improvement, I would like to know about sandbox but not in the context of Android development (and when I click on the link I get the same page?). Just created a github account and will put the issue there too

Sander

VSV Marketing Hi VSV!

That's correct, although the registration process is completely on its own. It's put next to the Android emulator setup as you'll will need it there once you set up the Android app (you can use the app to connect to the Sandbox environment to make it easier to perform certain actions). To avoid the need to duplicate the data multiple times I had linked to it from other sections. 🙂 It might be that the link doesn't work immediately as the content is loaded dynamically, in the introduction section there's a bullet about the Android emulator/account setup, you can click it there as well. Then scroll a little down and find the information to get your accounts on the sandbox environment. Please note that it's not possible to register on Sandbox through the apps, no support employees monitor the messages/signups there. 🙂

Deddo

Sander Deddo here on a business account, for some reason I turned cyan 🤔 Don't see any difference on the page docs.bunq.com and docs.bunq.com/#/android-emulator and only a very android specific explanation to get a key in the last paragraph of the Android Emulator section somewhere in the middle of the page, both on Chrome and Firefox. Can you paste the sandbox key instructions here so I can understand to what you are referring?

Sander

VSV Marketing Ah I see the links try to open in a new window, killing the jump to the section they should jump to. 🙈

The text I referred to is:

Creating an account or logging in

The first time you open the app you will be asked to verify your phonenumber. Sandbox however does not send actual SMS messages. Enter any valid phonenumber and use the default verification code 123456. This will work for all numbers.

Get tinker for the language of your choice.

Once installed, run tinker/user-overview, this will create an account for you when necessary.

The output of the command above will show you the login credentials for your sandbox account.

It is not possible to create accounts using the regular signup in the app, bunq is not reviewing Sandbox applications.

(especially the 3rd+4th points are relevant for you in this case to create accounts in case you do not need the app)

Deddo

Sander Ok, see what you are referring to. This is present on both pages but I guess thr page jump link is not working corectly as I now understand the intention from the link in the introduction to jump to the content somewhere in the middlw. As I am not familiar with tinker I used the tip from a post of Bastiaan to use a curl request to get a sandbox api key, this worked for me so maybe include this as an alternative. So maybe put the sandbox API part and options on a higher level on the page, then link to it fron the introduction. Are you the person who can do this?

Sander

VSV Marketing the best place to report this is https://github.com/bunq/doc/issues, or in case you do not have a GitHub account, you can also poke one of the support employees and they can report it to the relevant people. 🙂

Deddo

Sander Already made specially for this a github request (thanking also @Bastiaan for his help), under nr 73 but OGKevin rejected it already 😣

Sander

VSV Marketing I published a short document that I had lying around just a few minutes ago; hopefully this already explains a bit of the Sandbox stuff at least. And I'm pretty sure the devs at bunq will find a way to improve the documentation further as well. Thanks for your input. 🙂

OGKevin

VSV Marketing no I did not :p maybe I wasn’t clear enough tho xD my bad. I was trying to start a discussion on why.

Deddo

Sander Thanx, with the two context configs now ready will start testing tonight, good to know the support from together and github is fast and to the point (another person (kojoru) seemed to be able to update the docs and in due time was going to do that.