Retrieve an account access consent
Get the details of the account access consent as described in the Open Banking official documentation.
See also Tutorials: Get account and transaction information.
Request
The ID of the account access consent.
The unique ID of the ASPSP that the request is issued to.
The ID of Revolut is 001580000103UAvAAM.
Pattern: Value must match regular expression ^(Mon|Tue|Wed|Thu|Fri|Sat|Sun), \d{2} (Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec) \d{4} \d{2}:\d{2}:\d{2} (GMT|UTC)$
An RFC4122 UUID used as a correlation ID.
The access token that you've generated. For more information, see Generate an access token.
The user agent that the PSU is using.
Response
Account Access Consents Read
An RFC4122 UUID used as a correlation ID.
Possible length: non-empty and <= 128 characters
The unique ID that is assigned to identify the account access consent resource.
The date and time when the account access consent was created.
All dates in the JSON payloads are represented in ISO 8601 date-time format. All date-time fields in responses must include the timezone.
For example: 2017-04-05T10:43:07+00:00.
Possible values: [Authorised, AwaitingAuthorisation, Rejected, Revoked]
The status of the account access consent.
The date and time when the account access consent was created.
All dates in the JSON payloads are represented in ISO 8601 date-time format. All date-time fields in responses must include the timezone.
For example: 2017-04-05T10:43:07+00:00.
Possible values: [ReadAccountsBasic, ReadAccountsDetail, ReadBalances, ReadBeneficiariesBasic, ReadBeneficiariesDetail, ReadDirectDebits, ReadOffers, ReadPAN, ReadParty, ReadPartyPSU, ReadProducts, ReadScheduledPaymentsBasic, ReadScheduledPaymentsDetail, ReadStandingOrdersBasic, ReadStandingOrdersDetail, ReadStatementsBasic, ReadStatementsDetail, ReadTransactionsBasic, ReadTransactionsCredits, ReadTransactionsDebits, ReadTransactionsDetail]
Possible number of items: non-empty
The type of data access to the account.
The date and time when the permission expires. If this is not specified, the permission is open ended.
All dates in the JSON payloads are represented in ISO 8601 date-time format. All date-time fields in responses must include the timezone.
For example: 2017-04-05T10:43:07+00:00.
The start date and time for the transaction query period. If this is not specified, the start date is open ended, and data is returned from the earliest available transaction.
All dates in the JSON payloads are represented in ISO 8601 date-time format. All date-time fields in responses must include the timezone.
For example: 2017-04-05T10:43:07+00:00.
The end date and time for the transaction query period. If this is not specified, the end date is open ended, and data is returned to the latest available transaction.
All dates in the JSON payloads are represented in ISO 8601 date-time format. All date-time fields in responses must include the timezone.
For example: 2017-04-05T10:43:07+00:00.
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.
Links relevant to the payload.
The absolute URI to the resource.
The absolute URI to the next pagination resource.
The absolute URI to the previous pagination resource.
Meta data relevant to the payload.
Used for pagination. Indicates how many pages of results are available.