Both AA and PDF appear in every contract on these pages. A single, unified
transactionId ties the
whole journey together — you use the same identifier for status polling, raw data fetch, and analytics,
regardless of whether the data ultimately arrived via AA or PDF.Integration Flow
A complete journey is tied together by the singletransaction_id returned in step 1.
AA is attempted first; the smart router transparently falls back to a PDF statement upload
when AA cannot deliver — all within the same journey and the same transaction_id.
Initiate Consent
Call
POST /v3/requestconsent to start the journey and receive a transaction_id. See
Initiate Consent.Redirect the user
Send the user to
webRedirectionUrl to complete the AA consent journey. See
User Redirection.Smart routing & fallback
AA is attempted first. If AA cannot deliver, the smart router falls back to PDF statement upload
within the same journey.
Track status
Monitor completion via webhook (recommended), status polling, or in-iframe UI events —
all covered on the Track Status page. Each surfaces the AA block,
the PDF block, and the routing decision.
Fetch data
Once the journey is
SUCCESS, retrieve the raw FI data or normalized analytics —
both on the Fetch Data page.Pages in this section
| Page | Description |
|---|---|
| Initiate Consent | Start the journey and obtain a transaction_id. |
| User Redirection | Redirect the user and handle the callback. |
| Track Status | Track the journey via webhook, status polling, or in-iframe UI events — covering AA, PDF, and the routing decision. |
| Fetch Data | Retrieve raw FI data (dataSource of AA or PDF) or normalized analytics. |
Base URL
Base URL (UAT / Production): Contact support@moneyone.in
Common Headers
Every API request on these pages uses the following 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 |
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.