Retrieve an orchestration deposit
Retrieve a specific deposit received by an orchestration address.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
ID of the user.
^user_[A-Za-z0-9]+$ID of the orchestration address.
ID of the orchestration deposit. Deterministically derived from the
provider's deposit reference and escrow wallet ID, so the same on-chain
deposit always maps to the same depositId across webhook re-deliveries.
Response
A single deposit record.
A single on-chain deposit detected for an orchestration address.
Deterministic UUID derived from (providerReferenceId, escrowWalletId). Stable across webhook re-deliveries.
ID of the batch that included this deposit. null while status=PENDING or status=IGNORED.
Decimal amount of the source token deposited (e.g. "100.500000").
Precision matches the token's on-chain decimals.
usdc, usdt Abbreviated chain name (e.g. BASE).
On-chain address that sent the deposit. Informational only.
On-chain transaction hash.
Per-deposit status.
PENDING— recorded, waiting to be rolled into a batch.BATCHED— included in a batch (batchIdis set).IGNORED— recorded but never batched. SeeignoredReasonfor why.REFUNDED— wasPENDINGwhen the address was deactivated; the funds were refunded in-kind to thewalletAddresssupplied at deactivation.
PENDING, BATCHED, IGNORED, REFUNDED Why a deposit was ignored. Funds remain in the escrow wallet — a Slack alert fires for manual ops follow-up.
ADDRESS_DEACTIVATED— the deposit arrived after the address was deactivated.UNSUPPORTED_TOKEN— the deposited token does not match the address's configuredsource.currency(e.g. USDT sent to a USDC-only address).
ADDRESS_DEACTIVATED, UNSUPPORTED_TOKEN