Process consent requests through Account Aggregator
POST/aaconsent/:ver/:lang
Manages the lifecycle of consent artifacts through the Consent Flow API as per ReBIT FIU 2.0.0 specifications.
This API handles various types of consent requests including:
- Bank account consent requests
- GSTN consent requests (for tax-related financial information)
- Multi-provider financial data aggregation
The request payload contains base64 encoded consent data that is passed through to the selected Account Aggregator provider without modification.
Request
Responses
- 200
- 400
- 401
- 403
- 500
Consent request processed successfully
Response Headers
x-jws-signature
JWS signature received from Service Provider response
Bad request - Invalid consent data or missing parameters
Unauthorized - Invalid JWT token or authentication failure
Forbidden - Missing required headers or invalid provider
Internal server error