OPopenbankinguk
Account Access Consents

Get an Account Access Consent

Changed on

Enables an AISP to retrieve the status of an AIS consent.

get/account-access-consents/{ConsentId}

Request

  • Base URL
    /open-banking/v4.0/aisp (relative, and the document was published on a file host, not at the API’s origin)
  • URL
    /open-banking/v4.0/aisp/account-access-consents/{ConsentId}
  • Auth
    OAuth 2
    Client credentials
    Token URL: https://authserver.example/token scopes: accounts

Path parameters

ConsentIdstring required

ConsentId

Headers

x-fapi-auth-datestring

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

x-fapi-customer-ip-addressstring

The PSU's IP address if the PSU is currently logged in with the TPP.

x-fapi-interaction-idstring

An RFC4122 UID used as a correlation id.

Authorizationstring required

An Authorisation Token as per https://tools.ietf.org/html/rfc6750

x-customer-user-agentstring

Indicates the user-agent that the PSU is using.

x-client-idstring

Only used if an ASPSP requires the client ID in order to return rate limit headers.

TPPs must refer to ASPSP developer portals for further information on any rate limit policies, if the headers are supported and any additional requirements.

This header must not be used for client authentication

Response

Account Access Consents Read

RiskOBRisk2 required

The Risk section is sent by the initiating party to the ASPSP. <br /> It is used to specify additional details for risk scoring for Account Info.

Example response

{
  "Data": {
    "CreationDateTime": "2024-05-29T00:00:00Z",
    "StatusReason": [
      {
        "StatusReasonCode": "U004",
        "StatusReasonDescription": "Permissions field is missing",
        "Path": "Data.Permissions"
      }
    ]
  }
}

Changes