Go-live checklist

What a production integration needs before it trades real assets: safe order retries, deduplicated webhooks, a synced clock, fresh nonces, key rotation and tolerant parsing.

Check each item in the sandbox, then place your first production order at the smallest amount a venue takes. Open an item for how.

​

Orders survive a crash

Store the idempotency key before you send

Persist {quoteId, idempotencyKey, exactBody}, then send POST /api/v1/orders; a retry sends the same key and body bytes (Retries and recovery).

Recover, never reorder

A timeout, 5xx or outcomeUnknown does not mean the order failed: replay with the same key, or find the order by its quote.

cURL

# When you cannot tell whether an order was placed, read it by its quote id before doing
# anything else. ordered: read the order at statusUrl. notOrdered: nothing was placed.
# unknown: wait, then read again.
recovered=$(tetrafi GET "/api/v1/orders/by-quote/$order_quote")
jq -c '{state, orderId, statusUrl}' <<<"$recovered" >&2
unordered=$(tetrafi GET "/api/v1/orders/by-quote/$quote_id")
jq -c '{state, expired}' <<<"$unordered" >&2

Order again only on a new quote

Order again only on a new quote, and only when the order is shown not to exist or ended without filling.

Follow every order to the end

Read its statusUrl until terminal is true, every 10 to 15 seconds or when a webhook arrives (Order status).

​

Webhooks are handled once

Verify the signature

Verify the signature over the raw body before parsing it.

Deduplicate on webhook-id

Deduplicate on webhook-id: deliveries arrive at least once and out of order.

Answer 2xx within 10 seconds

Answer 2xx within 10 seconds, then work. Read statusUrl for the current state.

Watch for a paused endpoint

Resume a paused endpoint and redeliver what it missed. The delivery log does not survive a TetraFi restart (Webhooks).

​

Signing holds up

Sync your clock with NTP

X-Timestamp must be within 300 seconds of TetraFi’s clock, and a write’s at most 10 seconds ahead.

Use fresh nonces

Generate every X-Nonce from a cryptographic random source, and sign each send, retries included, with a new nonce and timestamp (Sign requests).

Keep secrets in a secret manager

Keep secrets in a secret manager, never in code or a tracked file.

​

Keys can be rotated

Pick up a rotated key within one hour

After Rotate key, the old key works for one hour (Rotate and revoke).

Grant only the permissions a key uses

Grant only the permissions a key uses.

Use a service account for software

Use a service account for software that should outlive one person’s access.

Know how to revoke a leaked key

Know how to revoke a leaked key at once.

​

Limits are respected

Watch markets with prices, never by polling quotes

Each key may send one live quote request every 3 seconds (Rate limits).

cURL

# Prices for the pair from memory: no venue is asked, so it costs no quote request.
# Each row is one venue, location and variant pair. Rows are indicative, never orderable.
path="/api/v1/prices?sell=$sell&buy=$buy&sellAmount=$amount"
prices=$(tetrafi GET "$path")
jq -c '{referenceMid: .referenceMid.buyPerSell, rows: [.rows[] | {venue: .venue.id,
  location: .location.kind, status, buy: .sizes[0].buy}]}' <<<"$prices" >&2

On any 429, wait Retry-After and retry once

On any 429, wait Retry-After seconds and retry once.

Requote a held quote

Requote a held quote instead of searching again (Requotes and expiry).

​

Parsing tolerates change

Ignore response fields you do not recognise

Ignore response fields you do not recognise.

Treat an unknown enum value as other

Treat an unknown enum value as “other”, such as a status, source reason or next.kind: keep following terminal, show detail or message, and carry on.

Match refusals on error, never message

Match refusals on error, never message, and treat an unknown code by its status class (Errors and refusals).

Parse amounts as decimals

Parse amounts as decimals, never floats (Conventions).

Read the Changelog before each release

Read the Changelog before each release of your integration.

​

Next

Retries and recovery

Retry an order safely and find out whether it was placed.

Webhooks

Receive order updates and recover missed deliveries.