Skip to main content
PATCH
/
account-access-consents
/
{ConsentId}
Error
A valid request URL is required to generate request examples
{
  "Errors": [
    {
      "Code": "AccessToken.Unauthorized",
      "Message": "<string>",
      "Path": "<string>",
      "Url": "<string>"
    }
  ]
}

Authorizations

​
Authorization
string
header
required

TPP confidential client authorization with the LFI to stage a consent. Please refer to OpenID FAPI Security Profile 1.0 -Part 2 Advanced - 5.2.2 point 14 - shall authenticate the confidential client using one of the following methods private_key_jwt and OpenID Connect Core 1.0 9. Client Authentication private_key_jwt

Headers

​
authorization
string
required

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

​
x-fapi-auth-date
string

The time when the User 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-address
string

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

​
x-fapi-interaction-id
string

An RFC4122 UID used as a correlation id.

​
x-customer-user-agent
string

Indicates the user-agent that the User is using.

Path Parameters

​
ConsentId
string
required

ConsentId

Body

Request Body

Patch Account Access Consent

​
Data
object

Primary data for the resource

​
Subscription
object

A Webhook Subscription Schema

Response

No Content