Sandbox

We do not use real money and do not allow external transactions in the sandbox environment.

Sandbox API keys

There are 4 ways to generate a bunq sandbox API key:

  1. create it from the sandbox app

  2. connect to Tinker (it will auto connect you to the sandbox; you can also use it to generate test users with working credentials for the sandbox bunq app)

  3. use Postman (<-- both the Sandbox and Production environments)

  4. run the cURL command

curl https://public-api.sandbox.bunq.com/v1/sandbox-user -X POST --header "Content-Type: application/json" --header "Cache-Control: none" --header "User-Agent: curl-request" --header "X-Bunq-Client-Request-Id: $(date)randomId" --header "X-Bunq-Language: nl_NL" --header "X-Bunq-Region: nl_NL" --header "X-Bunq-Geolocation: 0 0 0 0 000"

Once you have your API key, create more sandbox users to use as test customer accounts users, and start playing with the API. The sandbox base url is https://public-api.sandbox.bunq.com/v1/.

Sandbox request signing

Though request signing is a must on production, you can choose to disable it on sandbox to simplify the testing. Here's how it works:

  1. Set the X-Bunq-Client-Signature header of the request to IGNORE_ONLY_FOR_TESTING.

  2. Send the request.

When ready to try your integration on production, remove the IGNORE_ONLY_FOR_TESTING header setting and implement signing in sandbox first. Make sure it works and then change the base URL to https://api.bunq.com.

Sandbox money

Without money, it's not always sunny in the sandbox world. Fortunately, getting money on the bunq sandbox is easy. All you need to do is ask Sugar Daddy for it.

Send a POST v1/request-inquiry request passing sugardaddy@bunq.com in the counterparty_alias field. Specify the type for the alias and set the allow_bunqme field.

{
"amount_inquired": {
"value": "100",
"currency": "EUR"
},
"counterparty_alias": {
"type": "EMAIL",
"value": "sugardaddy@bunq.com",
"name": "Sugar Daddy"
},
"description": "You're the best!",
"allow_bunqme": false
}