FIP API Specification
Last updated
Was this helpful?
Last updated
Was this helpful?
This API enables an AA to discover accounts belonging to a customer based on the customer identifiers. A list of masked account information and corresponding linkRefNumber for each discovered account is returned based on the identifier matching logic at FIP.
<br>Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/Accounts/discover
aa_api_key is provided to FIP by the AA
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
List of financial information types.
API version.
Request creation timestamp.
Unique transaction identifier used for providing an end to end traceability.
This block would contain the information about the customer including the identifiers & the customer address at the AA
This API will be used for initiating an account link request to link selected account/s with the AA customer address. <br>Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/Accounts/link
aa_api_key is provided to FIP by the AA
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
Current Timestamp
Unique transaction identifier used for providing an end to end traceability.
Customer identifiers including AA virtual address.
This API will be used to delete a previously established account link to the user's profile. Once deleted, the financial information can not be retrieved for that account through Account Aggregator.
<br>Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/Accounts/delink
aa_api_key is provided to FIP by the AA
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.
Unique transaction identifier used for providing an end to end traceability.
This API is used to submit the token/OTP(received from the customer) back to FIP so that account linkage can be completed. It is used only in case of token-based authentication for linking accounts. <br>Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/Accounts/link/verify
aa_api_key is provided to FIP by the AA
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.
Unique transaction identifier used for providing an end to end traceability.
Temporary reference number generated by FIP for account linking request
The token that was sent to the customer by the FIP to confirm account link activity
This API is used by the AA to request for financial information from the FIP. The FIP will validate the request against the signed consent and return a sessionID which can then be used by the AA to fetch the required data.
<br>Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/FI/request
aa_api_key is provided to FIP by the AA
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
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.
Unique transaction identifier used for providing an end to end traceability.
Consent Artefact details.
Specifies the date time range for which the financial information is requested
This API is used to fetch financial information from FIP once AA recieves the data ready notification.
<br>Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/FI/fetch
aa_api_key is provided to FIP by the AA
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.
Unique transaction identifier used for providing an end to end traceability.
A session ID is a base-64 encoded UUID number that FIP returns to the AA for each financial information access request.
FIP ID as defined in the Account Aggregator Ecosystem.
This API is intended to be used by AA to notify the change in consent status due to the consent management operations performed by the customer. For more details about consent notification flow, please refer FAQ section. <br>Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/Consent/Notification
aa_api_key is provided to FIP by the AA
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.
Information about the notifier
Contains the Consent ID and Consent Status details.
This API will be used by the AA to send the consent artefact to the FIP on creation.
<br>Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/Consent
aa_api_key is provided to FIP by the AA
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
Specifies the status of consent artefact
ACTIVE
, PAUSED
, REVOKED
, EXPIRED
Consent artefact signed using JWS. See SignedConsentDetail model for consent format.
API version
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.
Creation time of the Consent Artefact
Section defining the parameters for consent tracking
This API can be used by the AAs to check availability of the FIP application.
<br>Note: "Request Body Example Value" and "Responses Example Value" given below is for illustrative purposes only.
/Heartbeat