Account access consents
The API specification for "account-access-consents" provided by Algbra's Open Banking API allows Third Party Providers (TPPs) to request and manage access to their customers' account information.
This API supports the creation, retrieval, and revocation of account access consents for customers of participating financial institutions. TPPs can use this API to request access to account information such as balance and transaction history, with the customer's explicit consent.
The API specification includes details on the endpoints, request and response formats, and authentication methods supported by the API.
- : Ability to read Accounts information
The unique id of the ASPSP to which the request is issued. The unique id will be issued by OB.
The time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is below: Sun, 10 Sep 2017 19:43:31 UTC
^(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)$The PSU's IP address if the PSU is currently logged in with the TPP.
An RFC4122 UID used as a correlation id.
An Authorisation Token as per https://tools.ietf.org/html/rfc6750 - required for API calls but may be ommited when using Swagger UI where the "Authorize" function has been operated
Indicates the user-agent that the PSU is using.
Account Access Consents Created
Bad request
Unauthorized
Forbidden
Not found
Method Not Allowed
Not Acceptable
Unsupported Media Type
Too Many Requests
Internal Server Error
POST /algbra/open-banking/v3.1/aisp/account-access-consents HTTP/1.1
Host: secure.tell.systems
Authorization: Bearer YOUR_OAUTH2_TOKEN
x-fapi-financial-id: text
Accept: */*
No content
- : Ability to read Accounts information
ConsentId
The unique id of the ASPSP to which the request is issued. The unique id will be issued by OB.
The time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is below: Sun, 10 Sep 2017 19:43:31 UTC
^(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)$The PSU's IP address if the PSU is currently logged in with the TPP.
An RFC4122 UID used as a correlation id.
An Authorisation Token as per https://tools.ietf.org/html/rfc6750 - required for API calls but may be ommited when using Swagger UI where the "Authorize" function has been operated
Indicates the user-agent that the PSU is using.
Account Access Consents Read
Bad request
Unauthorized
Forbidden
Not found
Method Not Allowed
Not Acceptable
Too Many Requests
Internal Server Error
GET /algbra/open-banking/v3.1/aisp/account-access-consents/{ConsentId} HTTP/1.1
Host: secure.tell.systems
Authorization: Bearer YOUR_OAUTH2_TOKEN
x-fapi-financial-id: text
Accept: */*
No content
- : Ability to read Accounts information
ConsentId
The unique id of the ASPSP to which the request is issued. The unique id will be issued by OB.
The time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is below: Sun, 10 Sep 2017 19:43:31 UTC
^(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)$The PSU's IP address if the PSU is currently logged in with the TPP.
An RFC4122 UID used as a correlation id.
An Authorisation Token as per https://tools.ietf.org/html/rfc6750 - required for API calls but may be ommited when using Swagger UI where the "Authorize" function has been operated
Indicates the user-agent that the PSU is using.
Account Access Consents Deleted
Bad request
Unauthorized
Forbidden
Not found
Method Not Allowed
Not Acceptable
Too Many Requests
Internal Server Error
DELETE /algbra/open-banking/v3.1/aisp/account-access-consents/{ConsentId} HTTP/1.1
Host: secure.tell.systems
Authorization: Bearer YOUR_OAUTH2_TOKEN
x-fapi-financial-id: text
Accept: */*
No content
Last updated