Orchestration Integration Guide

Index

Overview
Integration Flow
Step 1: Initiate Consent
Step 2: User Redirection
Step 3: Status Tracking
Step 4: Fetch Data
UI Events (postMessage API)
Quick Reference

Overview

This guide describes the end-to-end integration flow for initiating user consent, handling user redirection, tracking transaction status, and fetching analytics data using the Intelligent Data Fetch system with AA + PDF fallback.

This integration uses a unified transactionId for all operations, simplifying the flow compared to the legacy consent-based approach.

Integration Flow

Initiate Consent

Call POST /v3/requestconsent to start the consent journey and receive a transaction_id

Redirect User

Redirect user to webRedirectionUrl to complete the consent journey

Track Status

Monitor status via webhook (recommended) or polling API

Fetch Data

Once eventStatus is SUCCESS, fetch analytics using /analytics/json, /analytics/xml, or /analytics/excel

Endpoint

POST /v3/requestconsent

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

Request Body

{
  "vua": "<mobile_number>@onemoney",
  "accountID": "<account_id>",
  "productIDList": ["<product_id_1>", "<product_id_2>"],
  "partyIdentifierValue": "<mobile_number>",
  "partyIdentifierType": "MOBILE",
  "redirectUrl": "<your_redirect_url>",
  "fipID": ["<fip_id_1>", "<fip_id_2>"],
  "pan": "<pan_number>",
  "checks_overrides": {
    "min_salary_value": 30000,
    "min_avg_balance": 50000
  }
}

Request Parameters

string

required

Virtual User Address (e.g., 9876543210@onemoney)

string

required

Unique account identifier

array

required

Array of product IDs for multi-consent. Use either this or productID

string

required

User identifier value (mobile, PAN, Aadhaar, etc.)

string

required

Type: MOBILE, PAN, AADHAR, EMAIL, DOB, GSTIN

string

Callback URL after consent journey

array

Array of FIP IDs for smart routing

string

PAN number (format: ABCDE1234F)

object

Configuration object for custom data range

object

Runtime, per-request thresholds for business-rule checks (see below)

Config Object (Optional)

{
  "config": {
    "fiDataRange": {
      "from": "2023-01-01T00:00:00.000Z",
      "to": "2024-01-01T00:00:00.000Z"
    }
  }
}

Checks Overrides (Optional)

Runtime, per-request thresholds for the business-rule checks evaluated during the journey. It is a flat key→value map where each key is the parameter name of a configurable check and each value is the threshold that check is evaluated against for this request. This lets you tune check thresholds per consent request without changing the configuration set up for your product.

{
  "checks_overrides": {
    "min_salary_value": 30000,
    "min_avg_balance": 50000
  }
}

If you want to set thresholds dynamically, pass the values in checks_overrides.
If you do not need dynamic thresholds, omit the field — the threshold configured for your product is used instead, with no API change required.
A key that does not match a configurable check is ignored.
The set of configurable checks and their parameter names are agreed during onboarding. To enable or change them, contact support@moneyone.in.

Sample Request

curl --location '<base_url>/v3/requestconsent' \
--header 'Content-Type: application/json' \
--header 'organisationId: <your_organisation_id>' \
--header 'client_id: <your_client_id>' \
--header 'client_secret: <your_client_secret>' \
--header 'appIdentifier: <your_app_identifier>' \
--data-raw '{
  "vua": "9876543210@onemoney",
  "accountID": "ACC001",
  "productIDList": ["PROD001"],
  "partyIdentifierValue": "9876543210",
  "partyIdentifierType": "MOBILE",
  "redirectUrl": "https://yourapp.com/callback"
}'

Response

{
  "ver": "1.21.0",
  "status": "success",
  "data": {
    "webRedirectionUrl": "<web_redirection_url>",
    "transaction_id": "<transaction_id>"
  },
  "message": "Success"
}

Store the transaction_id for future reference. The webRedirectionUrl contains a time-bound access_token - do not modify it.

Step 2: User Redirection

Redirect the user to the webRedirectionUrl received in Step 1.

Post-Journey Redirect

After completing the consent journey, users are automatically redirected to your redirectUrl with the following parameters:

Parameter	Description
`txnid`	Transaction identifier
`status`	Journey status (`true` = success, `false` = failure)

Example:

https://yourapp.com/callback?txnid=abc123&status=true

To configure additional redirect URL parameters, contact support@moneyone.in.

Step 3: Status Tracking

You can track the transaction status using one of the following methods:

Webhook (Recommended)
Polling API

Configure a webhook endpoint to receive status updates when the transaction reaches a terminal state.

Webhook Payload - Successful AA Flow

{
  "timestamp": "2026-03-31T08:02:45.111480334Z",
  "transactionID": "ad277c38-ca13-49b0-befd-38343e221e6b",
  "eventType": "JOURNEY_COMPLETE",
  "eventStatus": "SUCCESS",
  "accountID": "ACC-78291",
  "eventData": [
    {
      "type": "AA",
      "status": "SUCCESS",
      "consents": [
        {
          "consentID": "6934dcbb-ee3f-4ea0-85dc-b564c9e5e1d2",
          "consentHandle": "7af9f26a-097c-4974-9e63-164a2b4c598e",
          "consentStatus": "CONSENT_APPROVED",
          "productID": "HOME2001",
          "fetchType": "PERIODIC",
          "fiFetch": "MANUAL",
          "dataFetchStatus": "SUCCESS",
          "accounts": [
            {
              "linkRefNumber": "9bd5e87a-7916-49ff-8ee1-969375f4f5e3",
              "fiStatus": "DELIVERED",
              "fipID": "finsharebank",
              "maskedAccountNumber": "XXXXXXXX1100",
              "checks": {
                "indicators": [
                  {
                    "check_id": "MIN_SALARY_15000",
                    "metadata": {
                      "salary": "12000"
                    },
                    "result": "FAILED"
                  }
                ]
              }
            }
          ]
        },
        {
          "consentID": "b1742f0c-3e9a-4d52-8c6b-1ae5d97f2034",
          "consentHandle": "c5e8a1b2-6f74-4390-a1d8-90b3e7c4f562",
          "consentStatus": "CONSENT_APPROVED",
          "productID": "HOME2001",
          "fetchType": "PERIODIC",
          "fiFetch": "MANUAL",
          "dataFetchStatus": "SUCCESS",
          "accounts": [
            {
              "linkRefNumber": "5c2f1ab9-3d47-4e8a-b6c1-7f9028d4e3a2",
              "fiStatus": "DELIVERED",
              "fipID": "finsharebank",
              "maskedAccountNumber": "XXXXXXXX2200",
              "checks": {
                "indicators": [
                  {
                    "check_id": "MIN_SALARY_15000",
                    "metadata": {
                      "salary": "40000"
                    },
                    "result": "PASS"
                  }
                ]
              }
            }
          ]
        },
        {
          "consentID": "02914fb5-0e4c-43dc-ae1b-d31fe3829c7b",
          "consentHandle": "b822049e-97f3-44d6-91fe-fa1bff1001db",
          "consentStatus": "CONSENT_APPROVED",
          "productID": "PL06S",
          "fetchType": "ONETIME",
          "fiFetch": "AUTOMATIC",
          "dataFetchStatus": "SUCCESS",
          "accounts": [
            {
              "linkRefNumber": "9bd5e87a-7916-49ff-8ee1-969375f4f5e3",
              "fiStatus": "DELIVERED",
              "fipID": "finsharebank",
              "maskedAccountNumber": "XXXXXXXX1100"
            }
          ]
        }
      ]
    },
    {
      "type": "PDF",
      "status": "SKIPPED",
      "accounts": []
    }
  ]
}

Webhook Payload - AA Failed with PDF Fallback

{
  "timestamp": "2026-03-31T06:59:46.465644026Z",
  "transactionID": "c664bcaa-c0bf-4101-b9ac-31e6d78cdb48",
  "eventType": "JOURNEY_COMPLETE",
  "eventStatus": "SUCCESS",
  "accountID": "ACC-90342",
  "eventData": [
    {
      "type": "AA",
      "status": "FAILED",
      "consents": [
        {
          "consentID": null,
          "consentHandle": "974e2b5d-196e-4965-bea2-eb5bcce88e01",
          "consentStatus": "CONSENT_REJECTED",
          "productID": null,
          "fetchType": null,
          "fiFetch": null,
          "dataFetchStatus": "NOT_ATTEMPTED",
          "accounts": []
        },
        {
          "consentID": null,
          "consentHandle": "44b0b90d-7593-462c-ae49-5bdb4b7ec6f8",
          "consentStatus": "CONSENT_REJECTED",
          "productID": null,
          "fetchType": null,
          "fiFetch": null,
          "dataFetchStatus": "NOT_ATTEMPTED",
          "accounts": []
        }
      ]
    },
    {
      "type": "PDF",
      "status": "SUCCESS",
      "accounts": [
        {
          "maskedAccountNumber": "10021535948",
          "bankName": "idfc",
          "accountType": "saving",
          "startDate": "02-09-2025",
          "endDate": "28-02-2026",
          "checks": {
            "indicators": [
              {
                "check_id": "MIN_SALARY_15000",
                "metadata": {
                  "salary": "40000"
                },
                "result": "PASS"
              }
            ]
          }
        }
      ]
    }
  ]
}

Webhook Payload - Journey Failed (Both Skipped)

{
  "timestamp": "2026-04-20T09:23:28.838168037Z",
  "transactionID": "d4e9259c-0ddb-437e-9955-6738f8a4caf1",
  "eventType": "JOURNEY_COMPLETE",
  "eventStatus": "FAILED",
  "accountID": "D2C20260420070500007248",
  "eventData": [
    {
      "type": "AA",
      "status": "SKIPPED",
      "consents": []
    },
    {
      "type": "PDF",
      "status": "SKIPPED",
      "accounts": []
    }
  ]
}

Webhook Payload Fields

Field	Description
`timestamp`	ISO 8601 timestamp of the event
`transactionID`	Transaction identifier
`eventType`	Type of event (`JOURNEY_COMPLETE`)
`eventStatus`	Overall status (`SUCCESS`, `FAILED`)
`accountID`	Account identifier
`eventData`	Array of step-level data

AA Flow Fields

Field	Description
`consents[].consentID`	Consent identifier (null if not created)
`consents[].consentHandle`	Consent handle
`consents[].consentStatus`	`CONSENT_APPROVED`, `CONSENT_REJECTED`
`consents[].productID`	Product ID (null if consent rejected)
`consents[].fetchType`	Fetch type (`PERIODIC`, `ONETIME`, null)
`consents[].fiFetch`	FI fetch mode (`MANUAL`, `AUTOMATIC`, null)
`consents[].dataFetchStatus`	`SUCCESS`, `FAILED`, `NO_DATA`, `NOT_ATTEMPTED`
`consents[].accounts[]`	Linked account details
`consents[].accounts[].linkRefNumber`	Link reference number
`consents[].accounts[].fiStatus`	FI status (`DELIVERED`)
`consents[].accounts[].fipID`	FIP identifier
`consents[].accounts[].maskedAccountNumber`	Masked account number
`consents[].accounts[].checks`	Business-rule checks evaluated for this account (see Checks)
`consents[].accounts[].checks.indicators[].check_id`	Identifier of the check (e.g., `MIN_SALARY_15000`)
`consents[].accounts[].checks.indicators[].metadata`	Map of source values used to evaluate the check
`consents[].accounts[].checks.indicators[].result`	Check outcome (`PASS`, `FAILED`)

PDF Flow Fields

Field	Description
`accounts[].maskedAccountNumber`	Account number
`accounts[].bankName`	Bank name
`accounts[].accountType`	Account type
`accounts[].startDate`	Statement start date
`accounts[].endDate`	Statement end date
`accounts[].checks`	Business-rule checks evaluated for this account (see Checks)
`accounts[].checks.indicators[].check_id`	Identifier of the check (e.g., `MIN_SALARY_15000`)
`accounts[].checks.indicators[].metadata`	Map of source values used to evaluate the check
`accounts[].checks.indicators[].result`	Check outcome (`PASS`, `FAILED`)

Checks

The checks object reports the outcome of business rules evaluated against each account’s data. It contains an indicators array, where each entry holds a check_id, its metadata, and the result. It appears per account under both AA consents and PDF accounts (in the webhook payload and Polling API), and per linkReferenceNumber in the Raw FI Data response.

"checks": {
  "indicators": [
    {
      "check_id": "MIN_SALARY_15000",
      "metadata": {
        "salary": "40000"
      },
      "result": "PASS"
    }
  ]
}

Field	Type	Description
`indicators`	array	List of evaluated checks
`indicators[].check_id`	string	Name of the check (e.g., `MIN_SALARY_15000`)
`indicators[].metadata`	object	Map of source values used to evaluate the check (e.g., `{"salary": "40000"}`)
`indicators[].result`	string	Check outcome — `PASS` or `FAILED`

To configure webhooks, contact support@moneyone.in.

Use this method only if webhook integration is not configured.

Endpoint

POST /transaction/status

Request

{
  "transactionId": "<transaction_id>"
}

Sample Request

curl --location '<base_url>/transaction/status' \
--header 'Content-Type: application/json' \
--header 'client_id: <your_client_id>' \
--header 'client_secret: <your_client_secret>' \
--header 'organisationId: <your_organisation_id>' \
--header 'appIdentifier: <your_app_identifier>' \
--data '{
  "transactionId": "<transaction_id>"
}'

Response

{
  "status": "SUCCESSFUL",
  "transaction_id": "<transaction_id>",
  "data": [
    {
      "type": "health_check",
      "status": "SUCCESSFUL",
      "data": {
        "healthy_fips": ["<fip_id_1>"],
        "unhealthy_fips": ["<fip_id_2>"],
        "fip_decisions": [
          {
            "fip": "<fip_id_1>",
            "decision": "FIP_HEALTHY"
          },
          {
            "fip": "<fip_id_2>",
            "decision": "FIP_UNHEALTHY"
          }
        ]
      }
    },
    {
      "type": "aa",
      "status": "SUCCESSFUL",
      "data": {
        "fips": [
          {
            "fip": "<fip_id_1>",
            "status": "DELIVERED"
          }
        ],
        "consents": [
          {
            "consentHandle": "<consent_handle>",
            "consentId": "<consent_id>",
            "consentStatus": "CONSENT_APPROVED",
            "productId": "<product_id>",
            "dataFetchStatus": "SUCCESS",
            "accounts": [
              {
                "linkRefNumber": "9bd5e87a-7916-49ff-8ee1-969375f4f5e3",
                "fiStatus": "DELIVERED",
                "fipID": "<fip_id_1>",
                "maskedAccountNumber": "XXXXXXXX1100",
                "checks": {
                  "indicators": [
                    {
                      "check_id": "MIN_SALARY_15000",
                      "metadata": {
                        "salary": "40000"
                      },
                      "result": "PASS"
                    }
                  ]
                }
              }
            ]
          }
        ]
      }
    },
    {
      "type": "pdf",
      "status": "SUCCESSFUL",
      "data": {
        "expected_fips": ["<fip_id_2>", "<fip_id_1>"],
        "total_expected": 2,
        "uploaded": 1,
        "processed": 1,
        "fetched": 1,
        "accounts": [
          {
            "maskedAccountNumber": "10021535948",
            "bankName": "idfc",
            "accountType": "saving",
            "startDate": "02-09-2025",
            "endDate": "28-02-2026",
            "checks": {
              "indicators": [
                {
                  "check_id": "MIN_SALARY_15000",
                  "metadata": {
                    "salary": "40000"
                  },
                  "result": "PASS"
                }
              ]
            }
          }
        ]
      }
    },
    {
      "type": "analytics",
      "status": "SUCCESSFUL"
    },
    {
      "type": "smart_routing_decision",
      "status": "SUCCESSFUL",
      "data": {
        "route": "AA"
      }
    }
  ],
  "message": null
}

Step Types

Type	Description
`health_check`	FIP health check results
`aa`	Account Aggregator flow status
`pdf`	PDF upload/parsing flow status
`analytics`	Analytics processing status
`smart_routing_decision`	Final routing decision (AA or PDF)

Step Statuses

Status	Description
`SUCCESSFUL`	Step completed successfully
`UNSUCCESSFUL`	Step failed
`FAILED`	Step failed (alternative)
`SKIPPED`	Step was skipped
`IN_PROGRESS`	Step is executing
`PENDING`	Step has not started
`PARTIAL`	Step partially completed

Overall Transaction Statuses

Status	Description
`SUCCESSFUL`	Transaction completed successfully
`UNSUCCESSFUL`	Transaction failed (includes cancelled/expired)
`IN_PROGRESS`	Transaction executing or awaiting input
`SKIPPED`	Transaction was skipped
`PENDING`	Transaction has not started

Step 4: Fetch Data

Once the data fetch is completed (eventStatus = SUCCESS), fetch raw FI data or analytics.

Available Endpoints

Type	Endpoint	Description
Raw FI Data	`POST /getallfidata`	Raw FI data (AA or PDF)
Analytics JSON	`POST /analytics/json`	Analytics in JSON format
Analytics XML	`POST /analytics/xml`	Analytics in XML format
Analytics Excel	`POST /analytics/excel`	Analytics as Excel file

Request Body

All endpoints use the same request body:

{
  "transactionId": "<transaction_id>"
}

Raw FI Data
Analytics JSON
Analytics XML
Analytics Excel

You can obtain the FI data two ways: pull it on demand with POST /getallfidata, or have it pushed to your webhook as soon as it is ready. Both carry the same FI data records.

Pull — POST /getallfidata
Push — Webhook

Endpoint

POST /getallfidata

Sample Request

curl --location '<base_url>/getallfidata' \
--header 'Content-Type: application/json' \
--header 'organisationId: <your_organisation_id>' \
--header 'client_id: <your_client_id>' \
--header 'client_secret: <your_client_secret>' \
--header 'appIdentifier: <your_app_identifier>' \
--data '{
    "transactionId": "<transaction_id>"
}'

Sample Response

{
  "ver": "1.21.0",
  "status": "success",
  "data": [
    {
      "linkReferenceNumber": "243212010002508",
      "maskedAccountNumber": "243212010002508",
      "fiType": "DEPOSIT",
      "bank": "ubi",
      "isTampered": false,
      "dataSource": "PDF",
      "checks": {
        "indicators": [
          {
            "check_id": "MIN_SALARY_15000",
            "metadata": {
              "salary": "40000"
            },
            "result": "PASS"
          }
        ]
      },
      "Profile": {
        "Holders": {
          "Holder": [
            {
              "name": "JOHN DOE",
              "mobile": "9876543210",
              "email": "john@example.com"
            }
          ]
        }
      },
      "Summary": {
        "currentBalance": "6981.1",
        "currency": "INR",
        "type": "saving",
        "ifscCode": "UBIN0824321"
      },
      "Transactions": {
        "startDate": "07-12-2024",
        "endDate": "25-01-2025",
        "Transaction": [
          {
            "type": "credit",
            "amount": "5500.0",
            "currentBalance": "5501.0",
            "transactionTimestamp": "10-12-2024",
            "narration": "UPI/TRANSFER"
          }
        ]
      },
      "type": "PDF"
    }
  ]
}

Response Fields

Field	Description
`data[].type`	Data source (`AA` or `PDF`)
`data[].fiType`	Financial information type (e.g., `DEPOSIT`)
`data[].isTampered`	Data tampering flag
`data[].Profile`	Account holder details
`data[].Summary`	Account summary
`data[].Transactions`	Transaction list
`data[].checks`	Business-rule checks evaluated for this account (see Checks)
`data[].checks.indicators[].check_id`	Identifier of the check (e.g., `MIN_SALARY_15000`)
`data[].checks.indicators[].metadata`	Map of source values used to evaluate the check
`data[].checks.indicators[].result`	Check outcome (`PASS`, `FAILED`)

The FI_DATA webhook fires when the workflow completes and financial data is ready. Unlike JOURNEY_COMPLETE (which reports consent status only), FI_DATA carries the actual account data — balances, transactions, and holder profile. AA and PDF accounts appear together in a single flat data[] array, each stamped with a type (AA or PDF) so you can tell which path delivered it.

{
  "timestamp": "2024-06-23T10:30:00.000Z",
  "transactionID": "txn_7f8a2b91c4d3e5f2",
  "eventType": "FI_DATA",
  "eventStatus": "SUCCESS",
  "accountID": "finpro_acc_381920",
  "data": [
    {
      "type": "AA",
      "linkReferenceNumber": "LRN-HDFC-SB-7821930",
      "maskedAccountNumber": "XXXXXXXX1234",
      "fiType": "DEPOSIT",
      "bank": "HDFC",
      "isTampered": false,
      "Profile": {
        "Holders": {
          "Holder": [
            { "name": "Rahul Sharma", "mobile": "9876543210", "email": "rahul@example.com", "pan": "ABCDE1234F" }
          ]
        }
      },
      "Summary": {
        "currentBalance": "150000.00",
        "currency": "INR",
        "type": "SAVINGS",
        "ifscCode": "HDFC0001234"
      },
      "Transactions": {
        "startDate": "2024-01-01",
        "endDate": "2024-06-23",
        "Transaction": [
          { "type": "CREDIT", "amount": "50000.00", "currentBalance": "150000.00", "transactionTimestamp": "2024-06-20T09:15:00Z", "narration": "NEFT TRANSFER FROM EMPLOYER ABC" },
          { "type": "DEBIT", "amount": "12500.00", "currentBalance": "137500.00", "transactionTimestamp": "2024-06-22T14:30:00Z", "narration": "UPI/PAYMENT/UTILITY/REF829341" }
        ]
      }
    },
    {
      "type": "PDF",
      "maskedAccountNumber": "XXXXXXXX5678",
      "fiType": "DEPOSIT",
      "bank": "SBI",
      "isTampered": false,
      "dataFetchTimeStamp": "2024-06-23T11:10:00.000Z",
      "Profile": {
        "Holders": {
          "Holder": [
            { "name": "Priya Menon", "mobile": "9123456780", "email": "priya@example.com", "pan": "FGHIJ5678K" }
          ]
        }
      },
      "Summary": {
        "currentBalance": "82300.00",
        "currency": "INR",
        "balanceDateTime": "2024-06-22T00:00:00Z",
        "type": "SAVINGS",
        "ifscCode": "SBIN0009876"
      },
      "Transactions": {
        "startDate": "2024-03-01",
        "endDate": "2024-06-22",
        "Transaction": [
          { "type": "CREDIT", "amount": "35000.00", "currentBalance": "82300.00", "transactionTimestamp": "2024-06-01T00:00:00Z", "valueDate": "2024-06-01", "narration": "SALARY JUNE 2024" },
          { "type": "DEBIT", "amount": "8200.00", "currentBalance": "74100.00", "transactionTimestamp": "2024-06-05T00:00:00Z", "valueDate": "2024-06-05", "narration": "EMI PAYMENT/LOAN/REF441" }
        ]
      }
    }
  ]
}

Each data[] item is an FI account object stamped with type. AA items carry linkReferenceNumber; PDF items carry dataFetchTimeStamp (and a valueDate on each transaction). The account fields (Profile, Summary, Transactions) match the POST /getallfidata items.

Field	Type	Description
`timestamp`	string	ISO-8601 UTC dispatch time
`transactionID`	string	Orchestration transaction ID
`eventType`	string	Always `FI_DATA`
`eventStatus`	string	`SUCCESS` (data present), `PARTIAL_SUCCESS` (some consents/statements failed), or `FAILED` (empty `data[]`)
`accountID`	string \| null	Account identifier (`null` if not provided)
`data[]`	array	Flat array of FI account objects mixing `AA` and `PDF` items
`data[].type`	string	`AA` or `PDF` — the discriminator for each item

FI_DATA is distinct from JOURNEY_COMPLETE, which reports consent status only. To receive FI data pushes, configure your webhook endpoint with support@moneyone.in.

Endpoint

POST /analytics/json

Sample Request

curl --location '<base_url>/analytics/json' \
--header 'Content-Type: application/json' \
--header 'organisationId: <your_organisation_id>' \
--header 'client_id: <your_client_id>' \
--header 'client_secret: <your_client_secret>' \
--header 'x-request-id: <unique_request_id>' \
--header 'appIdentifier: <your_app_identifier>' \
--data '{
    "transactionId": "<transaction_id>"
}'

Endpoint

POST /analytics/xml

Sample Request

curl --location '<base_url>/analytics/xml' \
--header 'Content-Type: application/json' \
--header 'organisationId: <your_organisation_id>' \
--header 'client_id: <your_client_id>' \
--header 'client_secret: <your_client_secret>' \
--header 'x-request-id: <unique_request_id>' \
--header 'appIdentifier: <your_app_identifier>' \
--data '{
    "transactionId": "<transaction_id>"
}'

Endpoint

POST /analytics/excel

Sample Request

curl --location '<base_url>/analytics/excel' \
--header 'Content-Type: application/json' \
--header 'organisationId: <your_organisation_id>' \
--header 'client_id: <your_client_id>' \
--header 'client_secret: <your_client_secret>' \
--header 'x-request-id: <unique_request_id>' \
--header 'appIdentifier: <your_app_identifier>' \
--data '{
    "transactionId": "<transaction_id>"
}'

Analytics output format is configurable. Contact support@moneyone.in to configure your preferred format.

UI Events (postMessage API)

When the orchestration UI is embedded in an iframe, it communicates with the parent window using the postMessage API.

Event Structure

{
  "type": "REDIRECT",
  "eventCode": "JOURNEY-SUCCESS",
  "message": "Workflow completed successfully for transaction <transaction_id>",
  "statusData": { ... }
}

Event Codes

Event Code	Trigger Condition	Description
`JOURNEY-SUCCESS`	`status === 'SUCCESSFUL'`	Workflow completed successfully
`JOURNEY-FAILURE`	`status === 'UNSUCCESSFUL'` or `'EXPIRED'` or `'CANCELLED'`	Workflow failed
`JOURNEY-SKIPPED`	`status === 'SKIPPED'`	Workflow was skipped
`JOURNEY-NETBANKING-REDIRECT`	Netbanking redirect required	User needs netbanking redirect

Listening for Events

window.addEventListener('message', (event) => {
  const { type, eventCode, message, statusData } = event.data;

  if (eventCode === 'JOURNEY-SUCCESS') {
    console.log('Workflow success:', statusData);
  } else if (eventCode === 'JOURNEY-FAILURE') {
    console.log('Workflow failed:', message);
  } else if (eventCode === 'JOURNEY-SKIPPED') {
    console.log('Workflow skipped:', message);
  }
});

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.

​Index

​Overview

​Integration Flow

​Step 1: Initiate Consent

​Endpoint

​Headers

​Request Body

​Request Parameters

​Config Object (Optional)

​Checks Overrides (Optional)

​Sample Request

​Response

​Step 2: User Redirection

​Post-Journey Redirect

​Step 3: Status Tracking

​Webhook Payload - Successful AA Flow

​Webhook Payload - AA Failed with PDF Fallback

​Webhook Payload - Journey Failed (Both Skipped)

​Webhook Payload Fields

​AA Flow Fields

​PDF Flow Fields

​Checks

​Endpoint

​Request

​Sample Request

​Response

​Step Types

​Step Statuses

​Overall Transaction Statuses

​Step 4: Fetch Data

​Available Endpoints

​Request Body

​Endpoint

​Sample Request

​Sample Response

​Response Fields

​Endpoint

​Sample Request

​Endpoint

​Sample Request

​Endpoint

​Sample Request

​UI Events (postMessage API)

​Event Structure

​Event Codes

​Listening for Events

​Quick Reference

​Endpoints

​Required Headers

Need Help?

Index

Overview

Integration Flow

Step 1: Initiate Consent

Endpoint

Headers

Request Body

Request Parameters

Config Object (Optional)

Checks Overrides (Optional)

Sample Request

Response

Step 2: User Redirection

Post-Journey Redirect

Step 3: Status Tracking

Webhook Payload - Successful AA Flow

Webhook Payload - AA Failed with PDF Fallback

Webhook Payload - Journey Failed (Both Skipped)

Webhook Payload Fields

AA Flow Fields

PDF Flow Fields

Checks

Endpoint

Request

Sample Request

Response

Step Types

Step Statuses

Overall Transaction Statuses

Step 4: Fetch Data

Available Endpoints

Request Body

Endpoint

Sample Request

Sample Response

Response Fields

Endpoint

Sample Request

Endpoint

Sample Request

Endpoint

Sample Request

UI Events (postMessage API)

Event Structure

Event Codes

Listening for Events

Quick Reference

Endpoints

Required Headers