transactionId. You initiate
a consent request, redirect the user to complete consent, track the journey to
completion (via webhook or polling), and then fetch the raw data and analytics.
This section covers the pure Account Aggregator flow. Every data item is sourced
from AA (
dataSource and type are always AA).Integration Flow
A complete AA integration is a four-step journey, all tied together by the singletransaction_id you receive in step 1. You initiate consent, hand the user off to the
hosted consent screen, track the journey to a terminal state, and then pull the data.
Initiate Consent
Call
POST /v3/requestconsent to start the journey. You receive a
webRedirectionUrl (the hosted consent screen) and a transaction_id to store and
reuse for every subsequent call. See Initiate Consent.Redirect the User
Send the user to the
webRedirectionUrl to approve consent in the Account Aggregator
flow. When the journey ends, the user is returned to your redirectUrl with the
outcome. See User Redirection.Track Status
Wait for completion using a terminal webhook push (recommended), by polling, or by
listening for in-iframe UI events — all covered on the single
Track Status page — until the transaction reaches a terminal
state (
SUCCESSFUL / UNSUCCESSFUL).Fetch Data
Once the journey is successful, retrieve the raw FI data or the computed analytics
(JSON, XML, or Excel) — both on the Fetch Data page — using the same
transaction_id.Pages in this section
| Page | Description |
|---|---|
| Initiate Consent | Start a journey and obtain the webRedirectionUrl and transaction_id. |
| User Redirection | Redirect the user to consent and handle the return to your app. |
| Track Status | Track the journey via webhook, status polling, or in-iframe UI events. |
| Fetch Data | Retrieve the raw FI data or computed analytics (JSON, XML, or Excel). |
Base URL & Headers
Base URL (UAT / Production): Contactsupport@moneyone.in.
All API requests use these headers:
| Header | Description |
|---|---|
Content-Type | application/json |
client_id | Your client ID |
client_secret | Your client secret |
organisationId | Your organisation ID |
appIdentifier | Your app identifier |
The analytics and data endpoints also accept an optional
x-request-id header
for request tracing.Quick Reference
Endpoints
| Action | Method | Endpoint |
|---|---|---|
| Initiate Consent | POST | /v3/requestconsent |
| Check Status | POST | /transaction/status |
| Fetch Raw FI Data | POST | /getallfidata |
| Fetch Analytics (JSON) | POST | /analytics/json |
| Fetch Analytics (XML) | POST | /analytics/xml |
| Fetch Analytics (Excel) | POST | /analytics/excel |
Required Headers
| Header | Required |
|---|---|
Content-Type | Yes |
client_id | Yes |
client_secret | Yes |
organisationId | Yes |
appIdentifier | Yes |
Need Help?
Contact support@moneyone.in for technical assistance or integration queries.