Track the lifecycle of a deposit
Returns the fill status of a deposit along with a corresponding fill transaction hash if filled. This endpoint loads data queried by an indexing service that polls relevant events on a 10-second cadence. Users should therefore expect an average latency of 1 to 15 seconds after submitting a deposit to see the status changed in this endpoint. This delay comes from the time it takes for the internal indexing to include the deposit transaction.
Authorization
bearerAuth API key for authentication.
In: header
Query Parameters
Chain Id where the deposit originated from. This must be used in conjunction with depositId. depositTxnRef is not required when using this parameter.
The deposit id that is emitted from the FundsDeposited event. This must be used in conjunction with originChainId. depositTxnRef is not required when using this parameter.
The deposit transaction hash that is emitted from the FundsDeposited event. For deposit-address (PDA) flows, pass the funding transaction — the transaction that sent funds to the deposit address. If you are using this, you do not need the other parameters (i.e. originChainId and depositId).
Exact PDA sweep/execution transaction reference — the transaction that moved funds out of a persistent deposit address into the bridge. Cannot be combined with any other selector. One sweep transaction can batch several deposit-address executions; use /deposits?sweepTxnRef= to list all of them.
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://across.to/api/deposit/status?originChainId=42161&depositId=3379116&depositTxnRef=0x56a86610aad2a653161c9dd4b4972f948198fd02ae9589cfac1d57bd86a156c1"{
"sweepTxnRef": null,
"actionsTargetRecipient": null,
"actionsTargetToken": null,
"actionsTargetAmount": null,
"actionsTargetTxnRef": null,
"actionsTargetBlockTimestamp": null,
"status": "filled",
"originChainId": 42161,
"depositId": "3379116",
"depositTxHash": "0x56a86610aad2a653161c9dd4b4972f948198fd02ae9589cfac1d57bd86a156c1",
"depositTxnRef": "0x56a86610aad2a653161c9dd4b4972f948198fd02ae9589cfac1d57bd86a156c1",
"fillTx": "0x7965d6064d8bee154d1c5471672180f5f802f789e22f66d54102a2010121a93e",
"fillTxnRef": "0x7965d6064d8bee154d1c5471672180f5f802f789e22f66d54102a2010121a93e",
"destinationChainId": 8453,
"depositRefundTxHash": null,
"depositRefundTxnRef": null,
"actionsSucceeded": null,
"actionsTargetChainId": null,
"pagination": {
"currentIndex": 0,
"maxIndex": 0
}
}{
"error": "IncorrectQueryParamsException",
"message": "Incorrect query params provided"
}{
"error": "DepositNotFoundException",
"message": "Deposit not found given the provided constraints"
}{
"error": "UnknownError",
"message": "Internal server error"
}Get all details for a single deposit GET
Returns a single deposit matching the provided query parameters. Searches across all deposit types: Across intents (V3FundsDeposited), CCTP (DepositForBurn), OFT (OFTSent). At least one of the following parameter combinations is required: 1. `depositTxnRef` 2. `depositId` AND `originChainId` 3. `relayDataHash` 4. `sweepTxnRef` Supply one selector per request (`depositId` + `originChainId` count as one). If a lookup can identify multiple transfers — for example a sweep transaction that executed several deposit-address transfers — use `/deposits` instead.
Get all deposits matching the given filters GET
Returns all deposits matching the given filters, newest first (ordered by `depositBlockTimestamp` descending). Filters combine with `AND`. `/deposits` is the endpoint to use when a transaction might identify multiple transfers. This endpoint loads data queried by an indexing service that polls relevant events on a 10-second cadence. Users should therefore expect an average latency of 1 to 15 seconds after submitting a deposit to see the status changed in this endpoint. This delay comes from the time it takes for the internal indexing to include the deposit transaction.