Queue a deposit for a passive-wallet account.
A passive wallet cannot sign, so rather than the account holder submitting a
signed deposit, this records the intent and Temple's engine performs the
deposit on their behalf.
This is not the deposit path for every account. Accounts on active
wallets sign their own deposits and are rejected here with
wallet_not_passive.
The request is an intent, not a deposit. The engine drains the queue and
removes entries as it processes them, so there is no status to poll — a
queued request has either not run yet or has already been actioned.
Completed deposits appear in GET /api/trading/deposits.
Limits. An account may hold at most 10 requests awaiting processing; the
next one is refused with too_many_pending_deposits until the queue drains.
Errors carry a machine-readable code:
| code | status | meaning |
|---|---|---|
wallet_not_linked | 409 | No wallet is linked to the account |
wallet_not_passive | 409 | The linked wallet signs its own deposits |
too_many_pending_deposits | 409 | 10 requests are already awaiting processing |
unknown_asset | 400 | asset_id is not a known instrument |
invalid_amount | 400 | Not a positive decimal, or more than 6 decimal places |
DEPOSITS_PAUSED | 423 | Deposits are temporarily paused |
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||