Description and Details
Updates the details of an existing AISP consent using a unique consent ID. This endpoint is typically used by a Third Party Provider (TPP) to modify consent parameters like expiration date, user info, permissions, and redirect settings.
Endpoint
https://api-dev-isolution.xyz/aisp/v1/access-consent/17500623575287883
HTTP Method
PUT
Headers Request Parameters
Header Name | Required | Description |
---|---|---|
Content-Type | Yes | application/json |
Authorization | Yes | Bearer token for access authentication |
X-Request-ID | Yes | Unique request ID for traceability |
Body Request Parameters
Field | Type | Required | Description |
---|---|---|---|
consentType | String | Yes | Type of consent (e.g., "AISP") |
expirationDateTime | String | Yes | ISO 8601 date-time when consent expires |
userId | String | Yes | Unique identifier of the user |
userName | String | Yes | Email or name of the user |
tppName | String | Yes | Name of the Third Party Provider |
tppRedirectURI | String | Yes | Redirect URI for post-consent flow |
tppState | String | Yes | State identifier used by the TPP |
tppKey | String | Yes | Key or secret issued to the TPP |
transactionFromDateTime | String | Yes | Start date of the transaction access window |
transactionToDateTime | String | Yes | End date of the transaction access window |
status | String | Yes | New status of the consent (e.g., "Authorised") |
permissions | Array | Yes | List of permissions being granted |
risk | Object | Optional | Risk section (can be an empty object) |
Response Parameters
Field | Type | Description |
---|---|---|
meta.code | String | HTTP status code (e.g., "200") |
meta.message | String | Message describing the update operation result |
HTTP Codes
Code | Description |
200 | Consent updated successfully |
400 | Bad request or invalid input |
401 | Unauthorized - missing/invalid token |
403 | Forbidden - permission denied |
404 | Consent ID not found |
500 | Internal server error |