# Bridge status

`GET https://api.getchord.xyz/v1/crosschain/status`

Source: https://getchord.xyz/docs/api-reference/operations/crosschainstatus/

Status of a bridge by its request id or deposit hash: `waiting` · `depositing` · `pending` · `submitted` · `success` · `delayed` · `refund` · `failure` · `unknown`.

## Parameters

| Name | In | Required | Type | Description |
| --- | --- | --- | --- | --- |
| `requestId` | query | yes | string | Request id (or the deposit tx hash on LI.FI). |
| `provider` | query | no | `lifi` · `relay` | Bridge provider. Chord uses `lifi`. |
| `fromChain` | query | no | integer |  |
| `toChain` | query | no | integer |  |

## Response 200

- **400**: Invalid parameters — `error` names the check that failed (`INVALID_PARAMS`, `BAD_ADDRESS`, `BAD_LIMIT`, `BAD_HOURS`, …).
- **429**: Over the per-minute limit (`RATE_LIMIT_EXCEEDED`). Read `X-RateLimit-Reset` and back off.
- **502**: The routing engine or an upstream did not answer (`ENGINE_ERROR`, `ROUTE_ERROR`).
- **503**: The lane behind this endpoint is not ready or not enabled here (`NOT_READY`, `CHAIN_NOT_ENABLED`, `NOT_ENABLED`, `*_UNAVAILABLE`). Retry later; do not treat it as an empty answer.