All Skills

Deposit Tracking

Track deposit lifecycle via GET /deposit/status. Covers status values, polling patterns, latency expectations, and bulk retrieval.

Edit

Deposit Tracking

Track the lifecycle of any Across deposit using the /deposit/status endpoint.

Endpoint

GET https://app.across.to/api/deposit/status

Query Parameters (use one of these combinations)

Option A: by transaction hash

ParameterDescription
depositTxnRefThe deposit transaction hash emitted by FundsDeposited

Option B: by chain + deposit ID

ParameterDescription
originChainIdChain ID where the deposit originated
depositIdDeposit ID emitted by FundsDeposited

Note: The API description states depositTxnRef is not required when using originChainId + depositId, even though the OpenAPI parameter list marks it as required. Set one of the two options explicitly.

Status Values

StatusMeaning
pendingDeposit has not been filled yet
filledFilled on destination chain; recipient has received funds
expiredDeposit expired and will not be filled; refund will be processed on origin chain
refundedDepositor has been refunded on origin chain

Response Fields (key)

Latency

This endpoint is backed by an indexing service that polls events on a 10-second cadence. Expect 1 to 15 seconds of latency after a deposit transaction is confirmed before the status updates.

Recommended Integration Pattern

  1. Store depositTxnRef (or originChainId + depositId) for each transaction your app initiates.
  2. Poll GET /deposit/status every 10 seconds to update your UI. Do not poll more frequently — the indexer cadence is 10 seconds.
  3. On mainnet, expect fills in ~2 seconds — most deposits resolve on the first or second poll.
  4. Show the fill transaction hash (fillTxnRef) when status is filled.
  5. Handle expired by informing the user that a refund is in progress.
  6. If using embedded actions (POST /swap/approval), check the actionsSucceeded field to verify destination actions executed.

Bulk Retrieval

To get all deposits for a given wallet:

GET https://app.across.to/api/deposits?depositor={address}

Supports:

Key fields returned per deposit include:

Important Notes