Sign in

v1

latestOpenAPI 3.0.0Apache 2.02026-07-134807111.3 MB
monetary-account-bank

Create new MonetaryAccountBank.

post/user/{userID}/monetary-account-bank

Path parameters

userIDinteger required

Headers

Cache-Controlstring

The standard HTTP Cache-Control header is required for all signed requests.

User-Agentstring required

The User-Agent header field should contain information about the user agent originating the request. There are no restrictions on the value of this header.

X-Bunq-Languagestring

The X-Bunq-Language header must contain a preferred language indication. The value of this header is formatted as a ISO 639-1 language code plus a ISO 3166-1 alpha-2 country code, separated by an underscore. Currently only the languages en_US and nl_NL are supported. Anything else will default to en_US.

X-Bunq-Regionstring

The X-Bunq-Region header must contain the region (country) of the client device. The value of this header is formatted as a ISO 639-1 language code plus a ISO 3166-1 alpha-2 country code, separated by an underscore.

X-Bunq-Client-Request-Idstring

This header must specify an ID with each request that is unique for the logged in user. There are no restrictions for the format of this ID. However, the server will respond with an error when the same ID is used again on the same DeviceServer.

X-Bunq-Geolocationstring

This header must specify the geolocation of the device. The format of this value is longitude latitude altitude radius country. The country is expected to be formatted of an ISO 3166-1 alpha-2 country code. When no geolocation is available or known the header must still be included but can be zero valued.

X-Bunq-Client-Authenticationstring required

The authentication token is used to authenticate the source of the API call. It is required by all API calls except for POST /v1/installation. It is important to note that the device and session calls are using the token from the response of the installation call, while all the other calls use the token from the response of the session-server call

Request body

currencystring

The currency of the MonetaryAccountBank as an ISO 4217 formatted currency code.

descriptionstring

The description of the MonetaryAccountBank. Defaults to 'bunq account'.

avatar_uuidstring

The UUID of the Avatar of the MonetaryAccountBank.

statusstring

The status of the MonetaryAccountBank. Can be: ACTIVE, BLOCKED, CANCELLED or PENDING_REOPEN

sub_statusstring

The sub-status of the MonetaryAccountBank providing extra information regarding the status. Will be NONE for ACTIVE or PENDING_REOPEN, COMPLETELY or ONLY_ACCEPTING_INCOMING for BLOCKED and REDEMPTION_INVOLUNTARY, REDEMPTION_VOLUNTARY or PERMANENT for CANCELLED.

reasonstring

The reason for voluntarily cancelling (closing) the MonetaryAccountBank, can only be OTHER.

reason_descriptionstring

The optional free-form reason for voluntarily cancelling (closing) the MonetaryAccountBank. Can be any user provided message.

display_namestring

The legal name of the user / company using this monetary account.

country_ibanstring

The country of the monetary account IBAN.

idinteger

The id of the MonetaryAccountBank.

createdstring

The timestamp of the MonetaryAccountBank's creation.

updatedstring

The timestamp of the MonetaryAccountBank's last update.

public_uuidstring

The MonetaryAccountBank's public UUID.

user_idinteger

The id of the User who owns the MonetaryAccountBank.

Response

With MonetaryAccountBank you can create a new bank account, retrieve information regarding your existing MonetaryAccountBanks and update specific fields of an existing MonetaryAccountBank. Examples of fields that can be updated are the description, the daily limit and the avatar of the account.<br/><br/>Notification filters can be set on a monetary account level to receive callbacks. For more information check the <a href="/api/1/page/callbacks">dedicated callbacks page</a>.