Description and Details
This API is used to authorise a previously created and updated consent by associating the consent ID with the user’s account(s). It marks the consent as authorised and ready for data access by the TPP (Third Party Provider).
Endpoint
https://api-dev-isolution.xyz/aisp/v1/access-consent/17505991469948315/authorization
Verb Method
POST
Headers Request Parameters
Key | Value | Description |
---|---|---|
Content-Type | application/json | Type of the request body |
Accept | / | Accepts all response types |
Cache-Control | no-cache | Disables caching |
User-Agent | PostmanRuntime/7.44.0 | Identifier for the HTTP client |
Accept-Encoding | gzip, deflate, br | Accepted encoding types |
Connection | keep-alive | Keeps the TCP connection open |
Host | Automatically calculated by Postman | |
Postman-Token | Token for request tracking |
Body Request Parameters
Parameter | Type | Description |
---|---|---|
accounts | Array | List of accounts linked to consent |
accountId | String | Unique identifier for the account |
accountAlias | String | User-defined label for account |
customerId | String | ID of the customer |
productType | String | Type of product (e.g., SAVINGS) |
productName | String | Name of the banking product |
category1 | String | General category (e.g., Banking) |
category2 | String | Sub-category (e.g., Personal) |
detailsExist | Boolean | Indicates if account details exist |
availableBalance | String | Available balance in the account |
Response Parameters
Parameter | Type | Description |
---|---|---|
meta | Object | Meta object containing status info |
meta.code | String | HTTP-like status code |
meta.message | String | Confirmation message |
HTTP Codes
Code | Meaning |
---|---|
200 | OK – Consent authorised successfully |
400 | Bad Request – Invalid or missing fields |
401 | Unauthorized – Invalid token/headers |
404 | Not Found – Consent ID does not exist |
500 | Internal Server Error – Server failure |