v50

latestOpenAPI 3.0.0open-licenceraw.githubusercontent.com2026-03-2029243564.9 KB
Account Access Consents

Create an Account Access Consent

Enables an AISP to ask an ASPSP to create a new account-access-consent resource, by sending a copy of the consent to the ASPSP.

post/account-access-consents

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

Request body

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.

Response

Account Access Consents Created

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"
      }
    ]
  }
}