AA API Specification
Last updated
Was this helpful?
Last updated
Was this helpful?
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.
<br>Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/Consent
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. <br/>Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e<br/> x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
API version
Creation timestamp of the message
The 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.
Specify the financial information types that customer wants to access
This 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. <br> Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/Consent/handle
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. <br/>Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e<br/> x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
API version
Creation timestamp of the message
The unique transaction identifier used for providing an end to end traceability.
Unique 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.
This API is intended for fetching the information associated with the specific consent. <br> Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/Consent/fetch
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. <br/>Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e<br/> x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
API version
Creation timestamp of the message
The unique transaction identifier used for providing an end to end traceability.
Unique ID generated by AA after consent approval is given by the customer.
This 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. <br> Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/FI/request
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. <br/>Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e<br/> x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
Contains the cryptographic parameters that are required to perform End-to-End encryption for sharing the financial information between the producer and the consumer in a secure manner. Please refer this link for more information: https://tools.ietf.org/html/rfc4492
API version
Creation timestamp of the message
The unique transaction identifier used for providing an end to end traceability.
Specifies the date time range for which the financial information is requested
This API is used to fetch financial information from AA once FIU recieves the data ready notification. <br> Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/FI/fetch
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. <br/>Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e<br/> x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
API version
Creation timestamp of the message.
Unique transaction identifier used for providing an end to end traceability.
A 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.
FIP ID as defined in the Account Aggregator Ecosystem.
This 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. <br> Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/Consent/Notification
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. <br/>Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e<br/> x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
API version
Creation timestamp of the message
The unique transaction identifier used for providing an end to end traceability.
Information about the notifier
Contains the Consent ID and Consent Status details.
This API can be used by AA Client, FIU and FIP to send notifications related to Financial Information (FI) fetch to AA. <br> Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/FI/Notification
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. <br/>Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e<br/> x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
API version
Creation timestamp of the message
The unique transaction identifier used for providing an end to end traceability.
Information about the notifier
Contains the financial information fetch session id and session status details.
This API can be used by FIP to send account linking related notifications to AA in case of direct authentication method of account linking. <br> Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/Account/link/Notification
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. <br/>Ex: x-request-meta: [Base64 of {"recipient-id": "SIMULATOR"}] i.e<br/> x-request-meta: eyJyZWNpcGllbnQtaWQiOiAiU0lNVUxBVE9SIn0K
API version
Creation timestamp of the message
The unique transaction identifier used for providing an end to end traceability.
Information about the notifier
This API can be used by FIPs and FIUs to check availability of AA Application.
<br> Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/Heartbeat
client_api_key is provided to AA by the AA Client or the FIU
fip_api_key is provided to AA by the FIP