Skip to main content
POST
/
orders
Create multiple orders
curl --request POST \
  --url https://clob.kuest.com/orders \
  --header 'Content-Type: application/json' \
  --header 'KUEST_ADDRESS: <kuest_address>' \
  --header 'KUEST_API_KEY: <kuest_api_key>' \
  --header 'KUEST_PASSPHRASE: <kuest_passphrase>' \
  --header 'KUEST_SIGNATURE: <kuest_signature>' \
  --header 'KUEST_TIMESTAMP: <kuest_timestamp>' \
  --data '
[
  {
    "order": {
      "tokenId": "<string>",
      "conditionId": "<string>",
      "maker": "<string>",
      "signer": "<string>",
      "taker": "<string>",
      "makerAmount": "<string>",
      "takerAmount": "<string>",
      "side": "BUY",
      "nonce": "<string>",
      "feeRateBps": "<string>",
      "salt": "<string>",
      "signatureType": 0,
      "signature": "<string>",
      "expiration": "<string>",
      "metadata": {}
    },
    "orderType": "FOK",
    "owner": "<string>",
    "postOnly": false
  }
]
'
[
  {
    "success": true,
    "errorMsg": "<string>",
    "orderId": "<string>",
    "orderHashes": [
      "<string>"
    ],
    "errorCode": "<string>"
  }
]
Submit up to 15 orders in one request. Every entry in the array shares the same payload shape as POST /order, so you can mix execution policies or token IDs while saving round trips.
Batch placement also requires L2 authentication headers: KUEST_ADDRESS, KUEST_SIGNATURE, KUEST_TIMESTAMP, KUEST_API_KEY, and KUEST_PASSPHRASE. Review the flow in the Authentication overview.
If the system-wide pause is active, the batch request responds with 409 and {"error":"system_paused"}. Books paused individually still return 409 along with {"error":"condition_paused"}. Every entry in the batch must use an owner value that matches KUEST_ADDRESS; otherwise the API returns 400 with {"error":"owner_address_mismatch"}.
Each entry in the response includes a status field with the same meanings described in Place single order (live, matched, delayed, or unmatched). Every array entry mirrors the single-order placement response structure, enabling you to inspect insert success, warnings, and order IDs independently. Need to check the final state of a submitted order? Call GET /data/order/{id}. To revoke any remaining quantity, use DELETE /order.

​
Batch item fields

Each array element accepts the same fields documented in POST /order. Provide the owner field alongside orderType and the nested order payload so it matches the KUEST_ADDRESS header. Key constraints repeated here for convenience:
FieldTypeRequiredDescription
ownerstringYesPolygon address that owns the API key. Must match the KUEST_ADDRESS header.
orderTypestringYesTime-in-force policy for the order (FOK, FAK, GTC, GTD).
postOnlybooleanNoWhen true, the order must rest on the book (GTC/GTD only).
orderobjectYesFull order payload identical to the single-order endpoint.
order.tokenIdstringYesIdentifier of the token/outcome being traded.
order.conditionIdstringYesMarket condition identifier tied to the token.
order.expirationstringConditionalRequired for GTD, optional elsewhere.
order.makerstringYesAddress that holds the asset being offered.
order.signerstringYesAddress that signed the order.
order.takerstringYesCounterparty address (use the zero address for open orders).
order.makerAmountstringYesMaker quantity with fixed precision.
order.takerAmountstringYesTaker quantity with fixed precision.
order.sidestringYesEither BUY or SELL.
order.metadataobject|nullNoOptional JSON metadata stored with the order.
order.noncestringYesMonotonic maker nonce.
order.feeRateBpsstringYesMaker fee rate in basis points.
order.saltstringYesUnique entropy for replay protection.
order.signatureTypenumberYes0 = EOA, 1 = proxy signer, 2 = Gnosis Safe signer.
order.signaturestringYesHex-encoded signature over the order payload.
order.metadata remains optional just like the single-order endpoint and can be omitted entirely in batch submissions. order.side must be the uppercase string BUY or SELL, and owner must align with the KUEST_ADDRESS header.

​
Order types

TypePartial fills?Rests on the book?Auto expiration?
FOK (Fill-Or-Kill)❌ No❌ No✅ Immediately if not 100% filled
FAK (Fill-And-Kill / IOC)✅ Yes❌ No✅ Any remaining size cancels right away
GTC (Good-Til-Cancelled)✅ Yes✅ Yes, until cancelled❌ No
GTD (Good-Til-Date)✅ Yes✅ Yes, until the given timestamp✅ At the specified expiration time
For GTD, remember the one-minute safety buffer: if the order should expire in 90 seconds, set expiration = now + 90 + 60.

​
Error codes

Batch responses reuse the same errorCode catalog as POST /order. Requests with fewer than 1 or more than 15 entries return HTTP 400 Bad Request without per-order results. When the batch exceeds the limit, the response body includes the message "batch supports at most 15 orders" to clarify the rejection.
errorCodesuccesserrorMsg (default)Notes
INVALID_ORDER_MIN_TICK_SIZEtrueorder is invalid. Price breaks minimum tick size rulesPrice implied by maker/taker amounts is outside the permitted [0, 1_000_000] window.
INVALID_ORDER_MIN_SIZEtrueorder is invalid. Size lower than the minimumMaker or taker amount is non-positive or below minimum size.
INVALID_ORDER_DUPLICATEDtrueorder is invalid. Duplicated. Same order has already been placed, can’t be placed againReserved for future duplicate protection.
INVALID_ORDER_NOT_ENOUGH_BALANCEtruenot enough balance / allowanceReserved for balance/allowance enforcement.
INVALID_ORDER_EXPIRATIONtrueinvalid expirationMissing, past, or negative expiration.
INVALID_ORDER_ERRORtruecould not insert orderGeneric validation failure.
EXECUTION_ERRORtruecould not run the executionInternal engine/database failure while inserting.
ORDER_DELAYEDfalseorder match delayed due to market conditionsReserved for delayed matching path.
DELAYING_ORDER_ERRORtrueerror delaying the orderReserved for delayed matching errors.
FOK_ORDER_NOT_FILLED_ERRORfalseorder couldn’t be fully filled, FOK orders are fully filled/killedReturned when a fill-or-kill order cannot fill 100%.
MARKET_NOT_READYfalsethe market is not yet ready to process new ordersReserved for markets warming up.

Headers

​
KUEST_ADDRESS
string
required

Checksummed wallet address performing the request.

​
KUEST_API_KEY
string<uuid>
required

API key obtained from the L1 derivation endpoint.

​
KUEST_PASSPHRASE
string
required

64 character hexadecimal passphrase associated with the API key.

​
KUEST_TIMESTAMP
string
required

Millisecond epoch timestamp (string) used for freshness checks.

​
KUEST_SIGNATURE
string
required

Hex-encoded HMAC-SHA256 signature built from the L2 signing string.

Body

application/json
Required array length: 1 - 15 elements
​
order
object
required
​
orderType
enum<string>
required

Time-in-force policy for the order.

Available options:
FOK,
FAK,
GTC,
GTD
​
owner
string
required

API key owner issuing the request.

​
postOnly
boolean
default:false

When true, the order must rest on the book (GTC/GTD only).

Response

Batch order placement results

​
success
boolean
required

Indicates whether the order was accepted.

​
errorMsg
string
required

Human-readable status for the placement.

​
orderId
string | null
required

ULID of the submitted order when accepted.

​
orderHashes
string[]
required

Settlement hashes for immediate matches (empty if none).

​
errorCode
string | null

Machine-readable error code when placement fails.