Go-live checklist

Production uses the same messages with real executions: limit orders rest, cancellations succeed, and fills follow the market. Before you ask Securitize for production access, confirm each item in sandbox.

#	Check	How to confirm it
1	A session opens end to end: `wss://`, a signed `hello` within 10 seconds, `welcome`, and a `ping` every 10 seconds	Run your client against sandbox for 15 minutes without a disconnect
2	Signatures cover the exact payload string sent: the payload is serialised once	Code review against Signing
3	Clocks are synchronised with NTP, and `TIMESTAMP_OUT_OF_WINDOW` raises an alert instead of a reconnect	Operations review
4	The private key is in a secrets store, is never logged, and belongs to a keypair that holds no assets	Secret scan and code review
5	Every message carries a unique `requestId` of at most 32 characters; replies are matched on it, and frames without one are handled as pushes	Code review
6	`externalRef` is derived from your own order id and stored before `place_order` is sent	Stop your process after the send and before the `ack`, resume, and check no second order exists
7	An `ack` with `UNKNOWN`, or an `UPSTREAM_UNAVAILABLE` error, is followed by `get_order` by `externalRef` before any resend	Code review against When an order is UNKNOWN
8	The client reconnects with backoff and, after every reconnect, reads back each working order with `get_order`	Close the socket while an order is working, and check your state matches `get_order`
9	Amounts are sent and read as decimal strings and compared as decimals	Code review
10	Decisions rest on `status` and `leavesQuantity`; an unknown status falls back to the quantities; quantities that do not reconcile stop processing and raise an alert	Code review against Orders and statuses
11	Buys are `LIMIT` orders by `quantity` sized within your `available` cash, and a refused buy raises an alert instead of a retry loop	Code review against Orders and statuses
12	Executions are summed on `effective` only; trades are deduplicated on `tradeId` and ordered by `executedAt`	Code review
13	CETs are reconciled on `amount`, only when `executionsComplete` is `true`; the `traceId` of every mint and burn is stored	Run the buy guide and the sell guide
14	A sell is placed by `quantity`, only after its CETs reach the redemption wallet	Run the sell guide
15	Every `error` is logged with its `code` and `traceId`	Log review

Practices that make these pass

One generic send(message) → reply helper that sets requestId, waits for the frame that echoes it, and times out. Every operation uses it.
Derive externalRef from your own primary key, prefixed by environment if you run several (prod-ord-000123).
Keep a small state per order in your own system (sent, acknowledged, working, done) and resume from it after a crash, reading the order back instead of replaying the flow.
Keep sandbox and production keys separate, so a production key can never reach the sandbox endpoint or the reverse.

Get started

Sandbox only

Guides

Concepts

Help

API reference

Practices that make these pass