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.
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 |
See also Tutorials: Get account and transaction information.
Authorization
Each Open Banking API must contain an authorization header in the following format to make a call: Bearer <yourAccessToken>
.
Before you start, ensure that you've got an access token with the correct scope
using the /token
endpoint.
You need to get the authorization code first and exchange it for an access token.
Never share your access_token
with anyone, as it can be used to access the banking data that you have access to and initiate transactions.
For more information, see Tutorial: Get account and transaction information and Tutorial: Initiate your first payment as examples.
x-jws-signature
Open Banking API Payment requests additionally require a JSON Web Signature (JWS) which needs to be added to the header of the request. The JWS signature must be obtained using the full content of the payload.
Request
Default
Response
Account Access Consents Created