> ## 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. # Get All Latest Data > Retrieve incremental financial data updates for periodic consent types, enabling efficient data synchronization without fetching complete historical records. ## Overview The Get All Latest Data API fetches incremental financial information (FI) that has been updated since the last data retrieval for consents configured with PERIODIC fetch type. This endpoint is designed to optimize data synchronization by returning only new or modified records, rather than the complete dataset each time. For ONETIME fetch type consents, there is no concept of incremental data. In such cases, this API returns the same response as the Get All FI Data endpoint, containing the complete dataset available for that consent. ## Use Cases This API is particularly useful for: * **Real-time account monitoring**: Applications that need to keep track of new transactions as they occur without repeatedly downloading the entire transaction history. * **Periodic data synchronization**: Systems that perform scheduled updates (daily, weekly, etc.) and only need to process changes since the last synchronization cycle. * **Personal Finance Management (PFM) applications**: Apps that display recent activity and need efficient backend updates to minimize data transfer and processing overhead. * **Spend analysis and categorization**: Services that analyze transaction patterns and only need to categorize new transactions rather than reprocessing historical data. ## Authentication All requests to this endpoint must include the following authentication headers: | Header | Type | Required | Description | | ---------------- | ------ | -------- | --------------------------------------------------------------------------------------------------------------------------------- | | `client_id` | string | Yes | The unique client identifier assigned to your organization during onboarding. This value is available in the FinPro admin portal. | | `client_secret` | string | Yes | The confidential client secret key paired with your client\_id. Store this securely and never expose it in client-side code. | | `organisationId` | string | Yes | Your organization's unique identifier in the FinPro system, used to scope all API requests to your tenant. | | `appIdentifier` | string | Yes | The application identifier that distinguishes different applications within your organization, useful for multi-product setups. | | `Content-Type` | string | Yes | Must be set to `application/json` to indicate the request body format. | ## HTTP Request ``` POST {{Base_URL}}/getalllatestfidata ``` ### Request Parameters | Parameter | Type | Required | Validation | Description | | ----------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | `consentID` | string | Yes | Must be a valid GUID (Globally Unique Identifier) provided by the Account Aggregator after consent approval. | The unique identifier for the consent record. This consent must be in ACTIVE status and have PERIODIC fetch type configured to receive incremental updates. | ### Request Body Example ```json theme={null} { "consentID": "3c92001e-57ea-4320-bbb8-66d524bfb435" } ``` ## Response Format ### Success Response A successful response returns a JSON object containing the incremental financial data for all accounts linked to the specified consent. #### Response Parameters | Parameter | Type | Required | Description | Supported Values | | ---------------------------------------------- | ------------ | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ver` | string | Yes | The version number of the API specification being used in this response. | e.g., "1.21.0" | | `status` | string | Yes | Indicates whether the request was processed successfully or encountered an error. | `success`, `failure` | | `data` | array | Yes | An array of account objects, each containing incremental data for a linked account. | Array of account data objects | | `data[].linkReferenceNumber` | string | Yes | The unique identifier linking this specific account to the consent. This reference is generated when an account is linked through the AA flow. | UUID format | | `data[].maskedAccountNumber` | string | Yes | The account number with most digits masked for security purposes, typically showing only the last 4 digits. | e.g., "XXXXXXXX3900" | | `data[].fiType` | string | Yes | Categorizes the type of financial information being shared from this account. | `DEPOSIT`, `TERM_DEPOSIT`, `TERM-DEPOSIT`, `RECURRING_DEPOSIT`, `SIP`, `CP`, `GOVT_SECURITIES`, `EQUITIES`, `BONDS`, `DEBENTURES`, `MUTUAL_FUNDS`, `ETF`, `IDR`, `CIS`, `AIF`, `INSURANCE_POLICIES`, `NPS`, `INVIT`, `REIT`, `GSTR1_3B`, `LIFE_INSURANCE`, `GENERAL_INSURANCE`, `OTHER` | | `data[].bank` | string | Yes | The name of the financial institution (bank or Financial Information Provider) holding this account. | e.g., "FinShareBankServer" | | `data[].Profile` | object | Yes | Contains comprehensive profile information about the account holder(s), including personal details and KYC status. | Profile object | | `data[].Profile.Holders.type` | string | Yes | Indicates whether the account has a single owner or multiple joint holders. | `SINGLE`, `JOINT` | | `data[].Profile.Holders.Holder` | object/array | Yes | Details about the account holder(s). For SINGLE type, this is an object; for JOINT type, this is an array of holder objects. | Holder object(s) | | `data[].Profile.Holders.Holder.name` | string | Yes | The full legal name of the account holder as registered with the financial institution. | Full name string | | `data[].Profile.Holders.Holder.dob` | string | Yes | The account holder's date of birth, used for identity verification and KYC compliance. | Date string (YYYY-MM-DD format) | | `data[].Profile.Holders.Holder.mobile` | string | Yes | The primary mobile number registered with the account, may be partially masked for privacy. | Mobile number string | | `data[].Profile.Holders.Holder.nominee` | string | Yes | Indicates whether a nominee has been registered for this account, important for succession planning and compliance. | `Registered`, `Not-Registered` | | `data[].Profile.Holders.Holder.landline` | string | Yes | The landline contact number if available, may be empty or partially masked. | Landline number string | | `data[].Profile.Holders.Holder.address` | string | Yes | The complete registered address for the account holder, may be partially masked for privacy. | Address string | | `data[].Profile.Holders.Holder.email` | string | Yes | The email address registered with the account, may be partially masked. | Email string | | `data[].Profile.Holders.Holder.pan` | string | Yes | The Permanent Account Number (PAN) issued by the Income Tax Department of India, used for tax compliance and identity verification. | PAN format string (e.g., "ABCDE1234F") | | `data[].Profile.Holders.Holder.ckycCompliance` | string | Yes | Indicates whether the Central KYC (CKYC) verification has been completed for this account holder, ensuring regulatory compliance across financial institutions. | `YES`, `NO`, `NO_DATA_AVAILABLE` | | `data[].Summary` | object | Yes | Provides a consolidated snapshot of the account's current state, including balance and account characteristics. | Summary object | | `data[].Summary.currentBalance` | string | Yes | The account balance as of the most recent update, represented as a string to preserve decimal precision. | Numeric string (e.g., "101666.33") | | `data[].Summary.currency` | string | Yes | The currency code in which the account balance is denominated. | ISO 4217 currency codes (e.g., "INR", "USD") | | `data[].Summary.exchgeRate` | string | Yes | The exchange rate applied if currency conversion is relevant, typically "1.0" for domestic accounts. | Numeric string | | `data[].Summary.balanceDateTime` | string | Yes | The exact timestamp when the current balance was calculated or last updated by the financial institution. | ISO 8601 timestamp | | `data[].Summary.type` | string | Yes | The operational classification of the account, determining transaction rules and features available. | `SAVINGS`, `CURRENT` | | `data[].Summary.branch` | string | Yes | The branch name or code where the account is held, useful for identifying the servicing location. | Branch identifier string | | `data[].Summary.facility` | string | Yes | Additional banking facilities associated with the account, such as overdraft protection. | e.g., "OD" (Overdraft), or empty string | | `data[].Summary.ifscCode` | string | Yes | The Indian Financial System Code uniquely identifying the bank branch, essential for electronic fund transfers (NEFT, RTGS, IMPS). | IFSC format string (e.g., "HDFC0001234") | | `data[].Summary.micrCode` | string | Yes | The Magnetic Ink Character Recognition code printed on cheques, used for check processing and clearance. | MICR format string (9 digits) | | `data[].Transactions` | object | Yes | Contains the incremental transaction data retrieved since the last fetch, organized by transaction type and time period. | Transactions object | ### Response Example ```json theme={null} { "ver": "1.21.0", "status": "success", "data": [ { "linkReferenceNumber": "e72534d6-0016-4f0e-9da5-3e05ad405394", "maskedAccountNumber": "XXXXXXXX3900", "fiType": "DEPOSIT", "bank": "FinShareBankServer", "Profile": { "Holders": { "type": "SINGLE", "Holder": { "name": "John Doe", "dob": "1990-01-15", "mobile": "9876543210", "nominee": "Registered", "landline": "", "address": "123 Main Street, Mumbai, Maharashtra - 400001", "email": "john.doe@example.com", "pan": "ABCDE1234F", "ckycCompliance": "YES" } } }, "Summary": { "currentBalance": "101666.33", "currency": "INR", "exchgeRate": "1.0", "balanceDateTime": "2025-11-14T10:30:00.000Z", "type": "SAVINGS", "branch": "Mumbai Central", "facility": "OD", "ifscCode": "FSBS0001234", "micrCode": "400211002" }, "Transactions": { "Transaction": [ { "txnId": "TXN123456789", "type": "CREDIT", "mode": "UPI", "amount": "5000.00", "currentBalance": "101666.33", "transactionTimestamp": "2025-11-13T14:25:30.000Z", "valueDate": "2025-11-13", "narration": "UPI/SALARY CREDIT/REF123", "reference": "REF123" } ] } } ] } ``` ## Error Handling ### Error Response Format When an error occurs during request processing, the API returns a standardized error response containing diagnostic information to help identify and resolve the issue. | Field | Type | Required | Description | | ----------- | ------ | -------- | ----------------------------------------------------------------------------------------------------------------- | | `ver` | string | Optional | The API version number, included when the error occurs after version validation. | | `timestamp` | string | Optional | The exact time when the error was encountered, useful for log correlation and debugging. | | `errorCode` | string | Optional | A machine-readable error identifier that categorizes the type of failure encountered. | | `errorMsg` | string | Optional | A human-readable description of the error, providing context about what went wrong and potentially how to fix it. | | `status` | string | Optional | Set to "failure" to indicate the request did not complete successfully. | ### Common Error Codes | Error Code | Error Message | Description | Resolution | | ------------------- | -------------------------------- | ------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- | | `InvalidRequest` | "consentID is required" | The request body is missing the mandatory consentID parameter. | Include a valid consentID in the request body. | | `InvalidConsentId` | "Consent ID does not exist" | The provided consent ID is not found in the system or belongs to a different organization. | Verify the consent ID is correct and was successfully created for your organization. | | `ConsentNotActive` | "Consent is not in active state" | The consent has been paused, revoked, or expired, preventing data access. | Check the consent status and obtain a new consent approval if needed. | | `NoIncrementalData` | "No new data available" | There have been no new transactions or updates since the last fetch for this consent. | This is informational; retry the request after the expected update interval. | | `Unauthorized` | "Invalid credentials" | The authentication headers are incorrect, missing, or the credentials have expired. | Verify your client\_id, client\_secret, organisationId, and appIdentifier are correct and active. | | `RateLimitExceeded` | "Too many requests" | The API rate limit has been exceeded for your organization. | Implement exponential backoff and reduce request frequency. Check rate limit headers in the response. | ### Error Response Example ```json theme={null} { "ver": "1.21.0", "timestamp": "2025-11-14T11:51:28.773Z", "errorCode": "InvalidConsentId", "errorMsg": "Consent ID does not exist.", "status": "failure" } ``` ## Usage Notes and Best Practices ### Periodic Fetch Type Requirement * This API is specifically designed for consents configured with **PERIODIC** fetch type, which enables incremental data updates at scheduled intervals. * For **ONETIME** fetch type consents, this API behaves identically to the Get All FI Data endpoint, returning the complete dataset since there is no incremental update mechanism. * Verify your consent template configuration in the FinPro admin portal to ensure the fetch type matches your integration requirements. ### Data Freshness and Polling Strategy * Implement a polling mechanism that respects the fetch frequency configured in your consent template (e.g., hourly, daily, weekly). * The incremental data returned represents updates since your last successful API call for that specific consent, tracked server-side by FinPro. * Consider implementing webhook listeners for DATA\_READY events to trigger data retrieval only when new information is available, rather than polling on a fixed schedule. ### Handling Multiple Accounts * A single consent may be linked to multiple financial accounts across different institutions (banks, mutual funds, insurance providers, etc.). * The response includes separate objects for each linked account, each containing its own incremental updates. * Process each account's data independently, as different accounts may have different update frequencies and data availability patterns. ### Data Completeness Considerations * Incremental data may not include all fields present in the initial full data fetch, focusing only on changed or new records (primarily new transactions). * If you need complete account information including profile details that rarely change, consider periodically calling the Get All FI Data endpoint to refresh your baseline dataset. * Transaction data is typically provided in reverse chronological order (most recent transactions first), though the exact ordering depends on the Financial Information Provider. ### Performance and Optimization * The incremental approach significantly reduces response payload sizes compared to fetching complete historical data, improving API response times and reducing bandwidth consumption. * For high-volume integrations with many consents, implement parallel API calls with appropriate rate limiting to efficiently process updates across your user base. * Cache account profile information (holder details, account characteristics) as this data changes infrequently, and focus incremental processing on transaction data. ### Consent Lifecycle Awareness * Always handle consent state transitions gracefully; a consent may become inactive between API calls due to user revocation, expiry, or pause actions. * Monitor webhook notifications for consent lifecycle events to maintain an accurate view of which consents are available for data retrieval. * Implement retry logic with exponential backoff for transient failures, but respect terminal error states (invalid consent, authorization failures) to avoid unnecessary API calls. ## Related Endpoints * **[Get All FI Data](/api-reference/data/get-all-fi-data)**: Retrieves the complete financial data for a consent, including full transaction history within the consent period. * **[Get FI Data](/api-reference/data/get-fi-data)**: Fetches data for a specific account identified by linkReferenceNumber, useful when you need to update information for just one account. * **[Get FI Data XML](/api-reference/data/get-fi-data-xml)**: Provides account data in XML format for integrations that require structured XML parsing rather than JSON. * **[Get FI Balance](/api-reference/data/get-fi-balance)**: Retrieves only the current balance information for accounts, optimized for display purposes without full transaction details. ## OpenAPI ````yaml POST /getalllatestfidata openapi: 3.0.3 info: title: FinPro API description: MoneyOne FinPro - Account Aggregator FIU Platform APIs version: 1.21.0 servers: - url: '{baseUrl}' description: FinPro API Server variables: baseUrl: default: https://scramblerpay-uat.moneyone.in description: API Base URL - change this to your environment security: - clientId: [] clientSecret: [] organisationId: [] appIdentifier: [] paths: /getalllatestfidata: post: tags: - Data Retrieval summary: Get All Latest Data description: >- Retrieve incremental financial data updates for periodic consent types, enabling efficient data synchronization without fetching complete historical records. For ONETIME fetch type consents, this API returns the same response as the Get All FI Data endpoint, containing the complete dataset available for that consent. operationId: getAllLatestFIData requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/GetAllLatestFIDataRequest' example: consentID: 3c92001e-57ea-4320-bbb8-66d524bfb435 responses: '200': description: Incremental financial data retrieved successfully content: application/json: schema: $ref: '#/components/schemas/GetAllLatestFIDataResponse' example: ver: 1.21.0 status: success data: - linkReferenceNumber: e72534d6-0016-4f0e-9da5-3e05ad405394 maskedAccountNumber: XXXXXXXX3900 fiType: DEPOSIT bank: FinShareBankServer Profile: Holders: type: SINGLE Holder: name: John Doe dob: '1990-01-15' mobile: '9876543210' nominee: Registered landline: '' address: 123 Main Street, Mumbai, Maharashtra - 400001 email: john.doe@example.com pan: ABCDE1234F ckycCompliance: 'YES' Summary: currentBalance: '101666.33' currency: INR exchgeRate: '1.0' balanceDateTime: '2025-11-14T10:30:00.000Z' type: SAVINGS branch: Mumbai Central facility: OD ifscCode: FSBS0001234 micrCode: '400211002' Transactions: Transaction: - txnId: TXN123456789 type: CREDIT mode: UPI amount: '5000.00' currentBalance: '101666.33' transactionTimestamp: '2025-11-13T14:25:30.000Z' valueDate: '2025-11-13' narration: UPI/SALARY CREDIT/REF123 reference: REF123 '400': description: Bad Request - Invalid consent ID or validation failure content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: invalidRequest: summary: Missing Consent ID value: ver: 1.21.0 timestamp: '2025-11-14T11:51:28.773Z' errorCode: InvalidRequest errorMsg: consentID is required status: failure invalidConsentId: summary: Invalid Consent ID value: ver: 1.21.0 timestamp: '2025-11-14T11:51:28.773Z' errorCode: InvalidConsentId errorMsg: Consent ID does not exist. status: failure consentNotActive: summary: Consent Not Active value: ver: 1.21.0 timestamp: '2025-11-14T11:51:28.773Z' errorCode: ConsentNotActive errorMsg: Consent is not in active state status: failure noIncrementalData: summary: No New Data Available value: ver: 1.21.0 timestamp: '2025-11-14T11:51:28.773Z' errorCode: NoIncrementalData errorMsg: No new data available status: failure '401': description: Authentication Failed - Invalid credentials content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: ver: 1.21.0 timestamp: '2025-11-14T11:51:28.773Z' errorCode: Unauthorized errorMsg: Invalid credentials status: failure '429': description: Too Many Requests - Rate limit exceeded content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: ver: 1.21.0 timestamp: '2025-11-14T11:51:28.773Z' errorCode: RateLimitExceeded errorMsg: Too many requests status: failure security: - clientId: [] clientSecret: [] organisationId: [] appIdentifier: [] components: schemas: GetAllLatestFIDataRequest: type: object required: - consentID description: Request body for retrieving incremental financial data updates. properties: consentID: type: string format: uuid description: >- The unique consent identifier (UUID) for which you want to retrieve incremental financial information. This must be an ACTIVE consent that has already been approved by the customer. For optimal results, use a consent with PERIODIC fetch type configured. GetAllLatestFIDataResponse: type: object description: >- Response containing incremental financial data for all accounts linked to the consent. properties: ver: type: string description: >- The version number of the API specification being used in this response. status: type: string enum: - success - failure description: >- Indicates whether the request was processed successfully or encountered an error. data: type: array description: >- An array of account objects, each containing incremental data for a linked account. items: $ref: '#/components/schemas/LatestFIAccountData' ErrorResponse: type: object properties: ver: type: string description: API version timestamp: type: string format: date-time description: When the error occurred errorCode: type: string description: Error category code errorMsg: type: string description: Detailed error message status: type: string description: FinPro-specific error code (FPxxxx format) LatestFIAccountData: type: object description: >- Incremental financial information for a single account including profile, summary, and new transactions. properties: linkReferenceNumber: type: string format: uuid description: >- The unique identifier linking this specific account to the consent. This reference is generated when an account is linked through the AA flow. maskedAccountNumber: type: string description: >- The account number with most digits masked for security purposes, typically showing only the last 4 digits (e.g., XXXXXXXX3900). fiType: type: string enum: - DEPOSIT - TERM_DEPOSIT - TERM-DEPOSIT - RECURRING_DEPOSIT - SIP - CP - GOVT_SECURITIES - EQUITIES - BONDS - DEBENTURES - MUTUAL_FUNDS - ETF - IDR - CIS - AIF - INSURANCE_POLICIES - NPS - INVIT - REIT - GSTR1_3B - LIFE_INSURANCE - GENERAL_INSURANCE - OTHER description: >- Categorizes the type of financial information being shared from this account. bank: type: string description: >- The name of the financial institution (bank or Financial Information Provider) holding this account. Profile: $ref: '#/components/schemas/LatestFIProfile' Summary: $ref: '#/components/schemas/LatestFISummary' Transactions: $ref: '#/components/schemas/LatestFITransactions' LatestFIProfile: type: object description: >- Contains comprehensive profile information about the account holder(s), including personal details and KYC status. properties: Holders: type: object description: Container for account holder information. properties: type: type: string enum: - SINGLE - JOINT description: >- Indicates whether the account has a single owner or multiple joint holders. Holder: $ref: '#/components/schemas/LatestFIHolder' LatestFISummary: type: object description: >- Provides a consolidated snapshot of the account's current state, including balance and account characteristics. properties: currentBalance: type: string description: >- The account balance as of the most recent update, represented as a string to preserve decimal precision (e.g., 101666.33). currency: type: string description: >- The currency code in which the account balance is denominated (ISO 4217 format, e.g., INR, USD). exchgeRate: type: string description: >- The exchange rate applied if currency conversion is relevant, typically 1.0 for domestic accounts. balanceDateTime: type: string format: date-time description: >- The exact timestamp when the current balance was calculated or last updated by the financial institution (ISO 8601 format). type: type: string enum: - SAVINGS - CURRENT description: >- The operational classification of the account, determining transaction rules and features available. branch: type: string description: >- The branch name or code where the account is held, useful for identifying the servicing location. facility: type: string description: >- Additional banking facilities associated with the account, such as OD (Overdraft), or empty string if none. ifscCode: type: string description: >- The Indian Financial System Code uniquely identifying the bank branch, essential for electronic fund transfers (NEFT, RTGS, IMPS). micrCode: type: string description: >- The Magnetic Ink Character Recognition code printed on cheques, used for check processing and clearance (9 digits). LatestFITransactions: type: object description: >- Contains the incremental transaction data retrieved since the last fetch. properties: Transaction: type: array description: >- Array of transaction records that have been added or updated since the last data retrieval. items: $ref: '#/components/schemas/LatestFITransaction' LatestFIHolder: type: object description: Details about an account holder. properties: name: type: string description: >- The full legal name of the account holder as registered with the financial institution. dob: type: string format: date description: >- The account holder's date of birth in YYYY-MM-DD format, used for identity verification and KYC compliance. mobile: type: string description: >- The primary mobile number registered with the account, may be partially masked for privacy. nominee: type: string enum: - Registered - Not-Registered description: >- Indicates whether a nominee has been registered for this account, important for succession planning and compliance. landline: type: string description: >- The landline contact number if available, may be empty or partially masked. address: type: string description: >- The complete registered address for the account holder, may be partially masked for privacy. email: type: string format: email description: >- The email address registered with the account, may be partially masked. pan: type: string description: >- The Permanent Account Number (PAN) issued by the Income Tax Department of India, used for tax compliance and identity verification (e.g., ABCDE1234F). ckycCompliance: type: string enum: - 'YES' - 'NO' - NO_DATA_AVAILABLE description: >- Indicates whether the Central KYC (CKYC) verification has been completed for this account holder, ensuring regulatory compliance across financial institutions. LatestFITransaction: type: object description: A single financial transaction record from the incremental data fetch. properties: txnId: type: string description: Unique transaction identifier assigned by the FIP. type: type: string enum: - CREDIT - DEBIT description: >- The type of transaction - CREDIT for money coming in, DEBIT for money going out. mode: type: string description: >- The mode or channel of the transaction (e.g., UPI, NEFT, IMPS, CARD, ATM, CASH). amount: type: string description: The transaction amount as a string to preserve decimal precision. currentBalance: type: string description: The account balance after this transaction was processed. transactionTimestamp: type: string format: date-time description: ISO 8601 timestamp when the transaction occurred. valueDate: type: string format: date description: The value date of the transaction in YYYY-MM-DD format. narration: type: string description: A description or narrative for the transaction provided by the FIP. reference: type: string description: A reference number or identifier associated with this transaction. securitySchemes: clientId: type: apiKey in: header name: client_id description: Your unique client identifier provided by MoneyOne during FIU onboarding clientSecret: type: apiKey in: header name: client_secret description: Your confidential client secret provided by MoneyOne organisationId: type: apiKey in: header name: organisationId description: Your organization's unique identifier in the FinPro system appIdentifier: type: apiKey in: header name: appIdentifier description: Application-specific identifier for tracking API calls ````