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      RequiredDescription
Content-Type      Yesapplication/json
Authorization      YesBearer token for access authentication
X-Request-ID      YesUnique request ID for traceability

Body Request Parameters
 

FieldTypeRequiredDescription
consentTypeStringYesType of consent (e.g., "AISP")
expirationDateTimeStringYesISO 8601 date-time when consent expires
userIdStringYesUnique identifier of the user
userNameStringYesEmail or name of the user
tppNameStringYesName of the Third Party Provider
tppRedirectURIStringYesRedirect URI for post-consent flow
tppStateStringYesState identifier used by the TPP
tppKeyStringYesKey or secret issued to the TPP
transactionFromDateTimeStringYesStart date of the transaction access window
transactionToDateTimeStringYesEnd date of the transaction access window
statusStringYesNew status of the consent (e.g., "Authorised")
permissionsArrayYesList of permissions being granted
riskObjectOptionalRisk section (can be an empty object)

Response Parameters

FieldTypeDescription
meta.codeStringHTTP status code (e.g., "200")
meta.messageStringMessage describing the update operation result

HTTP Codes

CodeDescription
200Consent updated successfully
400Bad request or invalid input
401Unauthorized - missing/invalid token
403Forbidden - permission denied
404Consent ID not found
500Internal server error