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

# List bridge deposits

> Read each bridge receipt and its separate payout or refund outcome

Use an active merchant API key with `read` scope to list your bridge deposits. Find a deposit by `id` in this paginated list or read it from its webhook payload.

**id** `string` *required*

Bridge request UUID returned by create.

## Query parameters

| Parameter | Values and behavior |
| - | - |
| `page` | Positive integer; default `1`. A page above the last nonempty page returns `400`. |
| `limit` | Positive integer; default `50`, reduced to `200` if larger. |
| `status` | `RECEIVED`, `PROCESSING`, `REQUIRES_REVIEW`, `FAILED`, `COMPLETED`, or `REVERSED`. |
| `from` | Deposit creation time in RFC3339, inclusive. |
| `to` | Deposit creation time in RFC3339, exclusive. |

Results are newest first. Send one value per parameter and omit unused filters. Empty, repeated, or invalid filter values return `400`.

```bash theme={"dark"}
curl --url 'https://api.daya.co/v1/bridges/750e8400-e29b-41d4-a716-446655440000/deposits?limit=50&page=1' \
  --header 'X-Api-Key: YOUR_API_KEY'
```

## Response

Returns `200` with `data`, `page`, `limit`, `total`, and `total_pages`. Empty results contain `data: []`, `total: 0`, and `total_pages: 0`. Each item contains:

| Field | Type | Meaning |
| - | - | - |
| `object` | string | Always `bridge.deposit`. |
| `id`, `bridge_id` | UUID strings | Deposit ID and owning request ID. |
| `status` | string | This deposit's [lifecycle status](/concepts/bridges#status-and-recovery). |
| `asset` | string | Received asset code, currently `USDT`. Handle future asset values without rejecting the response. |
| `amount` | decimal string | Deposited amount at the token's precision, including 18 places for BSC USDT. A full refund returns this amount. |
| `fee` | decimal string or null | Bridge fee in token units, with six decimal places, when available. |
| `payout_amount` | decimal string or null | Recipient amount after the fee, with six decimal places, when available. |
| `tx_hash` | string or null | Deposit transaction hash. |
| `flag_code`, `flag_message` | string or null | Reason the deposit needs attention. |
| `payout`, `refund` | object or null | Payout or refund details, when available. |
| `created_at` | RFC3339 string | Deposit creation time. |

Each non-null `payout` or `refund` contains only:

| Field | Type | Meaning |
| - | - | - |
| `status` | string | `PROCESSING`, `REQUIRES_REVIEW`, `FAILED`, or `COMPLETED`. |
| `tx_hash` | string or null | Hash for this outgoing transfer, separate from the receipt hash. |
| `failure_code`, `failure_message` | string or null | Failure details. Codes can include `PAYOUT_FAILED`, `PAYOUT_CANCELLED`, and `REFUND_FAILED`. |

Unavailable values are null. Read the request for destination addresses and the deposit for amounts. Use the deposit status to confirm the outcome: `COMPLETED` for a payout or `REVERSED` for a refund.

### Flag codes

Use `flag_code` to choose the next action. `flag_message` provides a readable explanation. Both are null when no condition needs attention.

| `flag_code` | Meaning and action |
| - | - |
| `LATE_DEPOSIT` | The deposit was processed too late after the payment deadline and is held for review. Contact support. |
| `BELOW_MINIMUM` | The deposit is below the `1`-token automatic minimum and is held for review. Contact support. |
| `REQUEST_LIMIT_EXCEEDED` | The deposit exceeds the remaining `100000`-token request limit and is held in full. Contact support. |
| `PAYOUT_FAILED` | The payout failed. Check `payout` and contact support. |
| `REQUIRES_REVIEW` | The deposit needs review. Contact support. |
| `BRIDGE_PAUSED` | The deposit is `PROCESSING`, but its payout or refund is waiting. Keep tracking its status. |
| `REFUND_IN_PROGRESS` | The deposit is `PROCESSING` and a refund is in progress. Track `refund` until the deposit becomes `REVERSED`. |

Contact [support@daya.co](mailto:support@daya.co) with the bridge and deposit IDs when help is needed. A held deposit will not pay out automatically. Do not send a replacement payment while the outcome is unknown, including while a payment or refund is waiting.

### Completed payout example

```json theme={"dark"}
{
  "data": [
    {
      "object": "bridge.deposit",
      "id": "850e8400-e29b-41d4-a716-446655440000",
      "bridge_id": "750e8400-e29b-41d4-a716-446655440000",
      "status": "COMPLETED",
      "asset": "USDT",
      "amount": "500.000000",
      "fee": "2.000000",
      "payout_amount": "498.000000",
      "tx_hash": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
      "flag_code": null,
      "flag_message": null,
      "payout": {
        "status": "COMPLETED",
        "tx_hash": "0xbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb",
        "failure_code": null,
        "failure_message": null
      },
      "refund": null,
      "created_at": "2026-10-11T12:05:00Z"
    }
  ],
  "page": 1,
  "limit": 50,
  "total": 1,
  "total_pages": 1
}
```

### Full refund example

This `data` item shows a refunded BSC deposit. The refund is the full `amount` of `0.500000000000000001` USDT, with no fee. The response retains `fee` and `payout_amount`; use `status` and `refund` to identify the completed refund.

```json theme={"dark"}
{
  "object": "bridge.deposit",
  "id": "860e8400-e29b-41d4-a716-446655440000",
  "bridge_id": "760e8400-e29b-41d4-a716-446655440000",
  "status": "REVERSED",
  "asset": "USDT",
  "amount": "0.500000000000000001",
  "fee": "0.005000",
  "payout_amount": "0.495000",
  "tx_hash": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
  "flag_code": null,
  "flag_message": null,
  "payout": null,
  "refund": {
    "status": "COMPLETED",
    "tx_hash": "0xcccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc",
    "failure_code": null,
    "failure_message": null
  },
  "created_at": "2026-10-11T12:05:00Z"
}
```

Invalid IDs or query parameters return `400`. Missing or other-merchant requests return `404`. Authentication and access errors use `401` and `403`; internal failures use `500`.

Payments sent with the wrong asset or chain do not appear in this list; contact [support@daya.co](mailto:support@daya.co) if a payment is missing. Use this endpoint, rather than `/v1/deposits` or payout lists, for bridge payments. See [refunds](/concepts/bridges#refunds).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.