Upcoming changes

January 15, 2020

  1. Due to internal backend changes, all active device-server installations created before April 9, 2019, will stop being validated on January 15, 2019. To communicate with the bunq API again, create a new API context.

  2. We are removing the limit_card_debit_replacement field from /v1/user/{user_id}/limit and are replacing it with limit_card_replacement.


December 17, 2019

It’s now possible to retrieve the tree planting progress of the user via the /user/{userID}/tree-progress endpoint.

December 11, 2019

  1. It’s now possible to order Green and Travel cards via the /user/{userID}/card-credit endpoint.

  2. We have changed the default SMS verification code for the sandbox app from 123456 to 992266.

October 9, 2019

We have replaced primary_account_numbers_virtual and primary_account_number_four_digit from the card resource with primary_account_numbers. The field returns the same string for primary_account_numbers and the same field + canceled cards for primary_account_numbers_virtual.

October 8, 2019

We have removed creating push notifications through updating notification_filters in the User and MonetaryAccount objects.

Instead, we introduced separate endpoints for the callbacks and notifications.

  • /v1/user/{userID}/notification-filter-push

  • /v1/user/{userID}/notification-filter-url

  • /v1/user/{userID}/monetary-account/{monetary-accountID}/notification-filter-push

  • /v1/user/{userID}/monetary-account/{monetary-accountID}/notification-filter-url

NOTE: When used via OAuth, the created push notifications expire in 90 days.

August 29, 2019

We have added the support of callbacks to OAuth.

July 9, 2019

We have removed the following share-invite-bank endpoints:

  • /user/{userID}/monetary-account/{monetary-accountID}/share-invite-bank-inquiry

  • /user/{userID}/monetary-account/{monetary-accountID}/share-invite-bank-inquiry/{itemId}

  • /user/{userID}/monetary-account/{monetary-accountID}/share-invite-bank-inquiry/{share-invite-bank-inquiryID}/amount-used/{itemId}

  • /user/{userID}/share-invite-bank-response

  • /user/{userID}/share-invite-bank-response/{itemId}

You can use the following endpoints instead:

  • /user/{userID}/monetary-account/{monetary-accountID}/share-invite-monetary-account-inquiry

  • /user/{userID}/monetary-account/{monetary-accountID}/share-invite-monetary-account-inquiry/{itemId}

  • /user/{userID}/monetary-account/{monetary-accountID}/share-invite-monetary-account-inquiry/{share-invite-monetary-account-inquiryID}/amount-used/{itemId}

  • /user/{userID}/share-invite-monetary-account-response

  • /user/{userID}/share-invite-monetary-account-response/{itemId}

July 2, 2019

  1. The type field has become mandatory for card-debit.

  2. We have deprecated the applied_limit field from the mastercard_action responses.

  3. We have removed the activation_code field from CardUpdate. Instead of using the field, set the status ACTIVE when the card has been ACCEPTED_FOR_PRODUCTION.

April 18, 2019

The old card limit fields in the card and card-batch objects have been deprecated and replaced with new ones. The default limit of €1,000 is now applied to all new cards.