Skip to main content
Sandbox only. Not part of the production API. In production, and anywhere they are not enabled, sandbox_deposit and sandbox_withdraw answer error MALFORMED with the message unsupported type "sandbox_deposit" (or "sandbox_withdraw"). Never build them into a production flow.
sandbox_deposit moves USD from Securitize into your own cash, and sandbox_withdraw moves it out, so you can fund yourself and test the cash flow end to end.

Request

Both are signed like place_order and need a key registered for trading; a read-only key answers NOT_PERMITTED. Both take the same payload:

sandbox_deposit

Moves USD from Securitize into your own cash.

sandbox_withdraw

Moves USD out of your own cash. It can take at most your available (see get_cash_balance_v2): the amount is held at once and counts in committed until it is booked, so it cannot be spent on a buy meanwhile.
A withdrawal for more than your available answers NOT_PERMITTED, and nothing is held.

The ack

The ack carries clientRef, amount, currency (USD) and a status: Once booked, the movement is pushed as cash_movement, a DEPOSIT or a WITHDRAW, and get_cash_balance_v2 and get_cash_movements show it.

Errors

A refusal answers error: Signature and timestamp errors are those of any signed message. See Signing. What each figure of your cash means is in Cash.