Getting sandbox money on the user account

The easiest way to become a millionaire is in our sandbox. This is because we have 1 user in our sandbox called Sugar Daddy. This user will approve all requests for money up to €500 at a time.

Call to SugarDaddy

As you can see in the response we'll need to pass in our user ID as well as monetary account ID. counterparty Alias is the alias (phone number, email address or IBAN) of the person you want money from. The amount and currency are €100.

Sugardaddy hands out free money, it's not unlimited. Sugardaddy will only accept requests up to €500,- Any request above that amount will be rejected.

Example request body

{
    "amount_inquired": {
        "value": "100",
    "currency": "EUR"
  },
    "counterparty_alias": {
      "type": "EMAIL",
      "value": "[email protected]",
      "name": "Sugar Daddy"
  },
  "description": "You'\''re the best!",
  "allow_bunqme": false
}'

Example curl call to sugardaddy

Example response body

Sugardaddy just returns a response with a request ID. But since we don't see an error we know that Sugardaddy received the request

Verification

If we want to double check that Sugar Daddy indeed paid us we'll have to double check our Monetary account again. Instead of listing all monetary accounts we can now also do a smaller API call to just get details for the monetary account in our request. Which should have our updated balance in the response

request

Response

Requesting money from other users

If you want to request money from other users then this is how you do it: Just be aware, sugardaddy is the only one who automatically transfers money to you.

get
/user/{userID}/monetary-account/{monetary-accountID}/request-inquiry

Get all payment requests for a user's monetary account. bunqme_share_url is always null if the counterparty is a bunq user.

Path parameters
userIDintegerRequired
monetary-accountIDintegerRequired
Header parameters
Cache-ControlstringOptional

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

User-AgentstringRequired

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-LanguagestringOptional

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-RegionstringOptional

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-IdstringOptional

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-GeolocationstringOptional

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-AuthenticationstringRequired

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

Responses
200

RequestInquiry, aka 'RFP' (Request for Payment), is one of the innovative features that bunq offers. To request payment from another bunq account a new Request Inquiry is created. As with payments you can add attachments to a RFP. Requests for Payment are the foundation for a number of consumer features like 'Split the bill' and 'Request forwarding'. We invite you to invent your own based on the bunq api!

application/json
get
/user/{userID}/monetary-account/{monetary-accountID}/request-inquiry

Response

Last updated

Was this helpful?