Accounts

Create an account access consent

Before you can access any data from a Revolut user, you must create an access consent to read data from the user's profile.

:::note When you create an account access consent, you must include a specific permission that follows the rules in the table below; otherwise, you get a 400 Bad request error. :::

Request Permissions

PERMISSIONS	DEPENDENCIES
ReadAccountsBasic	None
ReadAccountsDetail	None
ReadBalances	None
ReadBeneficiariesBasic	None
ReadBeneficiariesDetail	None
ReadDirectDebits	None
ReadScheduledPaymentsBasic	None
ReadScheduledPaymentsDetail	None
ReadStandingOrdersBasic	None
ReadStandingOrdersDetail	None
ReadTransactionsBasic	None
ReadTransactionsCredits	ReadTransactionsBasic OR ReadTransactionsDetail
ReadTransactionsDebits	ReadTransactionsBasic OR ReadTransactionsDetail
ReadTransactionsDetail	None

post/account-access-consents

Request

Base URL
https://oba-auth.revolut.com
Auth
API key in header Authorization

Headers

x-fapi-financial-idstring required

The unique ID of the ASPSP that the request is issued to. The ID of Revolut is 001580000103UAvAAM.

x-fapi-customer-last-logged-timestring

The date and time when the PSU last logged in with the TPP.

All dates in the HTTP headers are represented as RFC 7231 Full Dates. For example: <nobr>Sun, 10 Sep 2017 19:43:31 UTC</nobr>.

x-fapi-customer-ip-addressstring

The IP address of the PSU if the PSU is logged in with the TPP.

x-fapi-interaction-idstring

An RFC4122 UUID used as a correlation ID.

Authorizationstring required

The access token that you've generated. For more information, see Generate an access token.

x-customer-user-agentstring

The user agent that the PSU is using.

Request body

RiskOBRisk2 required

The Risk section contains the risk indicators that the initiating party sends to the ASPSP, which can be used to specify additional details for risk scoring for account information.

Response

Account Access Consents Created