> ## Documentation Index
> Fetch the complete documentation index at: https://developer.moneyone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Request consent across multiple FIUs in one call, with a single combined approval screen, as a Super App or LSP integrating with MoneyOne.

A Lending Service Provider (LSP) or Super App fronts several real, RBI-regulated
Financial Information Users (FIUs) — lenders — under the Account Aggregator (AA)
framework. Neither is itself a regulated FIU. Ordinarily, each FIU runs its own
separate consent flow. This integration model lets you request consent across
**multiple FIUs and products in a single call**, and gives your customer **one
combined approval screen** instead of one per FIU.

Every request and response in this integration is JSON over HTTPS, authenticated with
HTTP Basic Auth on every call.

## Integration Flow

A complete integration is a five-step journey, tied together by the single
`transactionId` you receive from Consent Creation. Discovering your entitled FIUs is a
read-only reference call you can make at any point in this flow — even before your
first Consent Creation call.

<Steps>
  <Step title="Discover Entitled FIUs (reference)">
    Call **List Entitled FIUs** at any time to confirm which `fiuId` values you're
    currently onboarded with, before naming them on Consent Creation. See
    [Entitled FIUs](./entitled-fius).
  </Step>

  <Step title="Initiate Consent">
    Call **Consent Creation** with the customer's details and the FIUs/products you
    need data for, in one call. You receive a `transactionId` and one combined
    `orchestrationWebUrl`. See [Initiate Consent](./initiate-consent).
  </Step>

  <Step title="Redirect the Customer">
    Redirect the customer to `orchestrationWebUrl`. They approve consent for every
    named FIU on one combined screen, hosted entirely by MoneyOne. See
    [User Redirection](./user-redirection).
  </Step>

  <Step title="Track Status">
    Track each consent to a terminal state via **Status Lookup** — either polling with
    just `transactionId`, or batch-looking-up specific consents/sessions/handles. See
    [Track Status](./track-status).
  </Step>

  <Step title="Request and Fetch Data">
    Once a consent is approved, explicitly trigger a data pull with **Data Request**,
    then retrieve the data with **Get FI Data** and derived insights with
    **Analytics**. See [Request Data](./request-data) and [Fetch Data](./fetch-data).
  </Step>
</Steps>

## Pages in this section

| Page                                   | Description                                                                 |
| -------------------------------------- | --------------------------------------------------------------------------- |
| [Initiate Consent](./initiate-consent) | Request consent across one or more FIUs and products in a single call.      |
| [Entitled FIUs](./entitled-fius)       | Discover which `fiuId` values you're currently onboarded with.              |
| [User Redirection](./user-redirection) | Redirect the customer to the combined consent screen and handle the return. |
| [Track Status](./track-status)         | Check the status of one or more consents, sessions, or handles.             |
| [Request Data](./request-data)         | Trigger a data pull for an already-approved consent.                        |
| [Fetch Data](./fetch-data)             | Retrieve the raw FI data and computed analytics for a consent.              |

Every endpoint requires HTTP Basic Auth (`client_id`/`client_secret`, issued at
onboarding) — see each page above for its exact method, path, and headers.

<Card title="Postman Collection" icon="flask" href="/lsp_postman_collection.json">
  Import pre-configured API collection for testing
</Card>