Place and cancel orders

A Trading Venue order is an EIP-712-signed intent from the maker wallet. You sign the order with the wallet's own key, submit it to the Platform API, and poll the queued reserved-balance transaction. The order becomes matchable only after its reservation confirms on-chain. This page covers placement, the intake checks that can reject an order, the order statuses, and cancellation. For depth, trades, and streams, see Read market data and streams.

Prerequisites

• An API key with an active organization, or an authenticated session.
• The maker wallet belongs to the selected participant and is registered in the deployment's identity registry for both listed tokens.
• The maker wallet holds a trading authorization to the market's venue contract that covers the reserved amount plus the maximum applicable fee. Intake rejects orders the authorization does not cover.
• A live market id from GET /api/v2/addons/trading-venue-markets.

Build and sign the order intent

The signature covers the on-chain order struct, so settlement can verify it independently of the platform. Sign with eth_signTypedData_v4 or your library's typed-data signer. Deployed smart accounts sign through ERC-1271.

The EIP-712 domain names the venue contract for the market:

{
  "name": "DALPTradingVenue",
  "version": "1",
  "chainId": 1,
  "verifyingContract": "0x9fE46736679d2D9a65F0992F2272dE9f3c7fa6e0"
}

Take verifyingContract from the market's venueAddress and chainId from the network the deployment runs on. The primary type is Order:

{
  "Order": [
    { "name": "maker", "type": "address" },
    { "name": "recipient", "type": "address" },
    { "name": "marketId", "type": "bytes32" },
    { "name": "side", "type": "uint8" },
    { "name": "priceTick", "type": "uint256" },
    { "name": "quantity", "type": "uint256" },
    { "name": "expiry", "type": "uint256" },
    { "name": "epoch", "type": "uint256" },
    { "name": "salt", "type": "uint256" },
    { "name": "maxFeeBps", "type": "uint256" }
  ]
}

Field semantics:

Place the order

Submit the signed intent with the API's market id. Amounts and prices travel as integer strings in token base units and price ticks.

curl -X POST "https://your-platform.example.com/api/v2/addons/trading-venue-orders" \
  -H "X-Api-Key: sm_dalp_xxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "marketId": "0198f1c4-5e6f-7a80-bc13-4d5e6f7a8b9c",
    "maker": "0x14dC79964da2C08b23698B3D3cc7Ca32193d9955",
    "recipient": "0x14dC79964da2C08b23698B3D3cc7Ca32193d9955",
    "side": "buy",
    "orderType": "limit",
    "timeInForce": "gtc",
    "priceTick": "1010",
    "quantity": "1000000000000000000",
    "expiry": "1785661200",
    "epoch": "0",
    "salt": "873245987234",
    "maxFeeBps": "25",
    "signature": "0x2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae1b"
  }'

timeInForce is gtc (good till cancelled), gtd (good till date, requiring a real expiry), or ioc (immediate or cancel); see time in force for the semantics. An optional triggerTick arms the order as a dormant stop instead of reserving it immediately; the stop contract is documented in Place stop orders. The platform verifies the signature, checks eligibility, desk limits, the trading authorization, and the fee cap, then queues the reserved-balance transaction and answers 202:

{
  "data": {
    "orderId": "0198f1c4-5e6f-7a80-bc13-4d5e6f7a8b9d",
    "orderHash": "0x2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae",
    "transactionHash": "0x2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae"
  },
  "meta": {
    "txHashes": ["0x2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae"]
  },
  "links": { "self": "/v2/addons/trading-venue-orders" }
}

A 202 body carries transactionId and statusUrl. Poll that URL until the write is confirmed; see Transaction tracking for the polling contract. Do not treat the order as placed before the reservation confirms: until then its status is pending_reservation, it is not matchable, and it does not appear in depth. With the TypeScript SDK, the same call is v2AddonsTradingVenueOrdersPlace from @settlemint/dalp-sdk/operations.

Track the order status

Read your working orders, filtered by market or status:

curl -X GET "https://your-platform.example.com/api/v2/addons/trading-venue-orders?status=working" \
  -H "X-Api-Key: sm_dalp_xxxxxxxxxxxxxxxx"

GET /api/v2/addons/trading-venue-reservations lists the reserved balances backing your open orders, and GET /api/v2/addons/trading-venue-blotter returns your fills with the fee charged to your side.

Cancel an order

Cancellation is effective on-chain, so a cancelled signed order can never fill, even if the venue matched it before the cancel arrived.

curl -X DELETE "https://your-platform.example.com/api/v2/addons/trading-venue-orders/0198f1c4-5e6f-7a80-bc13-4d5e6f7a8b9d" \
  -H "X-Api-Key: sm_dalp_xxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{}'

The platform marks the order cancelled on the book and queues the on-chain cancellation; the response is the same 202 shape as placement. The reserved balance is released when the cancellation confirms. Poll the statusUrl before you treat the order as cancelled on chain. The SDK operation is v2AddonsTradingVenueOrdersCancel.

Errors

Related

• Read market data and streams for depth, trades, candles, and the live stream.
• Place stop orders and use time in force for stops, GTD, and IOC.
• Quote in bulk for batched place, replace, and cancel with net-delta reservations.
• Trade through sessions and auctions for what placement does in each session state.
• Trading venue order lifecycle for the full state model behind these statuses.
• Transaction tracking for the 202 polling contract.