AA API Specification
Was this helpful?
Was this helpful?
This API can be used by FIPs and FIUs to check availability of AA Application.
Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
client_api_key is provided to AA by the AA Client or the FIU
fip_api_key is provided to AA by the FIP
This API is intended for AA Client to request generation of digitally signed consent artefacts. The customer has to use the AA application to select accounts and approve consent generation. Once the customer approves the consent request on the AA application, AA generates the digitally signed consent artefacts. Note - The AA Client never sees the account of the customer or directly participates in consent generation.
Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
client_api_key is provided to AA by the AA Client or the FIU
Detached JWS of the body
It is the Base64 encoded JSON object having the identifier of the receiver to whom the API call needs to be forwarded. Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
This call generated via AA client.
API version
2.0.0Creation timestamp of the message
2023-06-26T11:39:57.153ZThe transaction identifier generated by the requester for providing an end to end traceability. The AA should use this transaction identifier in the responses and notifications for FIU to correlate response with the request. The transaction identifier will be a UUID generated string.
4a4adbbe-29ae-11e8-a8d7-0289437bf331This API is intended to be used by FIU/AA Client to check the consent status and retrieve the consent ID from AA once the consent is approved by customer. Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
client_api_key is provided to AA by the AA Client or the FIU
Detached JWS of the body
It is the Base64 encoded JSON object having the identifier of the receiver (recipient-id) to whom the API call needs to be forwarded. Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
API version
2.0.0Creation timestamp of the message
2023-06-26T11:39:57.153ZThe unique transaction identifier used for providing an end to end traceability.
795038d3-86fb-4d3a-a681-2d39e8f4fc3cUnique ID generated by AA after receiving the consent request. Consent Handle can be used by FIU/AA Client to check the consent status and retrieve the consent ID once the consent is approved by customer.
39e108fe-9243-11e8-b9f2-0256d88baae8This API is intended for fetching the information associated with the specific consent. Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
client_api_key is provided to AA by the AA Client or the FIU
fip_api_key is provided to AA by the FIP
Detached JWS of the body
It is the Base64 encoded JSON object having the identifier of the receiver to whom the API call needs to be forwarded. Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
API version
2.0.0Creation timestamp of the message
2023-06-26T11:39:57.153ZThe unique transaction identifier used for providing an end to end traceability.
0b811819-9044-4856-b0ee-8c88035f8858Unique ID generated by AA after consent approval is given by the customer.
654024c8-29c8-11e8-8868-0289437bf331This API is used by the FIU to request for financial information from the AA. The AA will validate the request against the signed consent and return a sessionID which can then be used by the FIU to fetch the required data. Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
client_api_key is provided to AA by the AA Client or the FIU
Detached JWS of the body
It is the Base64 encoded JSON object having the identifier of the receiver to whom the API call needs to be forwarded. Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
API version
2.0.0Creation timestamp of the message
2023-06-26T11:39:57.153ZThe unique transaction identifier used for providing an end to end traceability.
e8cc6822-d4bb-4eb1-9e1b-4996fbff8acbThis API is used to fetch financial information from AA once FIU recieves the data ready notification. Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
client_api_key is provided to AA by the AA Client or the FIU
Detached JWS of the body
It is the Base64 encoded JSON object having the identifier of the receiver to whom the API call needs to be forwarded. Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
A request to fetch FI data from AA against given sessionId.
API version
2.0.0Creation timestamp of the message.
2023-06-26T11:39:57.153ZUnique transaction identifier used for providing an end to end traceability.
3dd436f8-0747-4a8f-9001-375e419430beA session ID is a base-64 encoded UUID number that an AA returns to the FIU or AA Client for each financial information access request.
caa2f259-2dc2-4075-87aa-6d81018b6183FIP ID as defined in the Account Aggregator Ecosystem.
FIP-1This API can be used by AA Client, FIU and FIP to place a request for consent status update to AA in specific use cases. For more details, please refer FAQ section. Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
client_api_key is provided to AA by the AA Client or the FIU
fip_api_key is provided to AA by the FIP
Detached JWS of the body
It is the Base64 encoded JSON object having the identifier of the receiver to whom the API call needs to be forwarded. Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
Status of the Consent.
API version
2.0.0Creation timestamp of the message
2023-06-26T11:39:57.153ZThe unique transaction identifier used for providing an end to end traceability.
0b811819-9044-4856-b0ee-8c88035f8858This API can be used by AA Client, FIU and FIP to send notifications related to Financial Information (FI) fetch to AA. Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
client_api_key is provided to AA by the AA Client or the FIU
fip_api_key is provided to AA by the FIP
Detached JWS of the body
It is the Base64 encoded JSON object having the identifier of the receiver to whom the API call needs to be forwarded. Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
API version
2.0.0Creation timestamp of the message
2023-06-26T11:39:57.153ZThe unique transaction identifier used for providing an end to end traceability.
0b811819-9044-4856-b0ee-8c88035f8858This API can be used by FIP to send account linking related notifications to AA in case of direct authentication method of account linking. Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
fip_api_key is provided to AA by the FIP
Detached JWS of the body
It is the Base64 encoded JSON object having the identifier of the receiver to whom the API call needs to be forwarded. Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
API version
2.0.0Creation timestamp of the message
2023-06-26T11:39:57.153ZThe unique transaction identifier used for providing an end to end traceability.
0b811819-9044-4856-b0ee-8c88035f8858