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

# Get Connection Data

After a customer completes the Meld Connect Widget flow, you can begin fetching their financial data — balances, owners, identifiers, transactions, and investments. This section is for developers building backend integrations that listen for connection completion, wait for data to be available, and call Meld's APIs to retrieve it.

## Before you begin

<Info>
  * A connection has been created through [Creating Connections](/docs/bank-linking/creating-connections)
  * A webhook profile is configured so you receive lifecycle events — see [Webhook Quickstart](/docs/bank-linking/onboarding/step-5-setting-up-webhooks/webhook-quickstart)
  * Your backend has access to the customer's `connectionId` or `customerId`
</Info>

## Steps

1. Review the [widget emitted events](/docs/bank-linking/get-connection-data/widget-emitted-events). These tell you when a connection has been successfully completed or if there was an error during the flow.
2. Understand [when your data is available](/docs/bank-linking/get-connection-data/when-is-your-data-available). Different products are aggregated on different timelines, and webhooks indicate when each is ready.
3. Once your data is available, [retrieve your connection data](/docs/bank-linking/get-connection-data/retrieving-connection-data). This covers balances, owners, identifiers, transactions, and investments.
4. Review the [connection statuses and errors](/docs/bank-linking/get-connection-data/connection-statuses-and-errors). As connections move out of `ACTIVE`, learn how to refresh, repair, or delete them in the next section.

The data Meld returns is normalized across providers — see [Data Normalization](/docs/bank-linking/get-connection-data/data-normalization) for details on signage, categories, and investment types.

## Informing the user of the status

<Tip>
  There will likely be a delay between your user completing the widget flow and you receiving webhooks indicating data is ready. This can be a few seconds for balance, identifier, and owner data, or several minutes for transactions on accounts with large histories. Show a loading state in your UI during this time so users don't think the connection failed and try again.
</Tip>

## Endpoint quick reference

| Data                    | Endpoint                                    | Reference                                                                                       |
| :---------------------- | :------------------------------------------ | :---------------------------------------------------------------------------------------------- |
| Balances / Owners / IDs | `GET /bank-linking/financial-accounts`      | [Retrieving Connection Data](/docs/bank-linking/get-connection-data/retrieving-connection-data) |
| Transactions            | `GET /bank-linking/transactions`            | [Retrieving Connection Data](/docs/bank-linking/get-connection-data/retrieving-connection-data) |
| Investment Holdings     | `GET /bank-linking/investment-holdings`     | [Retrieving Connection Data](/docs/bank-linking/get-connection-data/retrieving-connection-data) |
| Investment Transactions | `GET /bank-linking/investment-transactions` | [Retrieving Connection Data](/docs/bank-linking/get-connection-data/retrieving-connection-data) |
| Connections metadata    | `GET /bank-linking/connections`             | [Retrieving Connection Data](/docs/bank-linking/get-connection-data/retrieving-connection-data) |

<Note>
  Refer to the [Bank Linking API reference](/api-reference/bank-linking) for the complete request and response schema for each endpoint.
</Note>