> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/api-reference/bridge/list-bridge-deposits.md).

# GET /api/v1/bridge/deposits

List bridge deposits.

`operationId`: `listBridgeDeposits`

**Authentication:** `hmacAuth`.

List the authenticated account's cross-chain deposits, newest first. Read-only: the watcher creates and advances these records, and this endpoint only reads them.

There is no pre-arrival state. A deposit exists only once the watcher observes an on-chain transfer, so every record carries a `tx_hash` and `log_index` (its id is `{tx_hash}:{log_index}`) and a confirmation count. A fiat-funded payment still in provider checkout is not yet a deposit and does not appear here.

Optional filters narrow by `chain`, `asset` and `status`; an unrecognized filter value simply matches nothing. Deposits are USDC or USDX only in this cut.

The list returns at most the newest 100 deposits and is not yet paginated: there is no cursor or time-window parameter, so an account with more than 100 deposits can only reach older ones by narrowing `chain`, `asset` or `status`. A cursor may be added later; doing so is additive.

## Parameters

| Name     | In    | Type                                                               | Required | Description                                                                                                         |
| -------- | ----- | ------------------------------------------------------------------ | -------- | ------------------------------------------------------------------------------------------------------------------- |
| `limit`  | query | `integer`                                                          | No       | Maximum records to return, 1-100. Values above the maximum are clamped to it; a non-integer or zero value is a 400. |
| `chain`  | query | `string`                                                           | No       | Filter by source chain, e.g. `ethereum`.                                                                            |
| `asset`  | query | `USDC` \| `USDX`                                                   | No       | Filter by deposited asset.                                                                                          |
| `status` | query | `detected` \| `confirming` \| `credited` \| `failed` \| `reverted` | No       | Filter by deposit status.                                                                                           |

## Responses

| Status | Body                                                                       | Meaning                        |
| ------ | -------------------------------------------------------------------------- | ------------------------------ |
| `200`  | array of [`BridgeDeposit`](/api-reference/guides/schemas.md#bridgedeposit) | Bridge deposits, newest first. |
| `400`  | — *(no schema declared)*                                                   | —                              |
| `401`  | — *(no schema declared)*                                                   | —                              |
| `429`  | — *(no schema declared)*                                                   | —                              |

## Example

```bash
curl -X GET 'https://exchange.nexus.xyz/api/exchange/api/v1/bridge/deposits' \
  -H 'X-API-Key: nx_7f3a1b...' \
  -H 'X-Timestamp: 1776033911836' \
  -H 'X-Signature: <hmac-sha256>'
```

***

<sub>Generated from</sub> <sub></sub><sub>`eng/apps/exchange/api/openapi.json`</sub> <sub></sub><sub>(spec</sub> <sub></sub><sub>`0.9.27`</sub><sub>). Do not edit by hand — regenerate with</sub> <sub></sub><sub>`python3 product/docs/tools/api-reference/generate.py`</sub><sub>. Hand-authored context lives in the Guides pages.</sub>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nexus.xyz/api-reference/bridge/list-bridge-deposits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.