Start building

Understand the integration sequence and its completion checks before connecting a live client.

1. Establish access and account scope#

Obtain the released authentication contract for your environment. Confirm the account your client can access. X-Omega-Account-Id selects that account; it does not authenticate the caller or grant spending authority.

Read access and authority.

2. Discover an exact market#

Read exchange metadata, resolve base and quote asset representation IDs, and retain decimals, price scale, price tick and quantity step. A symbol alone is not enough to route funds.

Review the market metadata and book examples. The examples use synthetic USD6 and EUR6 assets.

3. Construct a bounded order#

Choose a market or limit order. Bind exact assets and quantity, and use explicit spend/receive bounds where required. Review fee treatment and signing limits before authorization. Never infer net output from the quoted price alone.

Compare the limit-order request and market-order request.

4. Persist, submit and reconcile#

Persist the selected account, request body, method/path and idempotency key before submission. Retain the returned operation and order IDs. After a lost acknowledgement, reconcile the original instruction rather than generating a new key.

A 202 response acknowledges processing. It does not mean the order is open, filled or settled. See order state and fills.

5. Verify the result#

Read immutable fills and their quantities, fees and settlement references. Account for filled quantity and remaining quantity separately. Keep ledger effects, settlement finality and any external delivery as separate observations.

Your integration is complete only when it can explain both the order outcome and the current state of the funds. Follow the settlement guide.