Batch cancel orders
Trading
Batch cancel orders
Cancel up to 100 CLOB orders across one or more markets in a single round-trip
DELETE
Batch cancel orders
Cancel up to 100 CLOB orders in a single request. Order IDs may belong to different markets and events. CLOB-only: any AMM order is rejected per-item withDocumentation Index
Fetch the complete documentation index at: https://docs.bayse.markets/llms.txt
Use this file to discover all available pages before exploring further.
UNSUPPORTED_ENGINE. Ownership is enforced upstream — order IDs the caller does not own return ORDER_NOT_FOUND.
See the Batch orders concept page for limits, semantics, and rate-limit behavior.
Authentication
Write authentication required —X-Public-Key, X-Timestamp, and X-Signature headers. See the Authentication guide.
Headers
Optional. 1–255 characters of
[A-Za-z0-9_-]. Retries within 24 hours that share the same key, body, and route replay the original response with Idempotent-Replayed: true. A retry with the same key but a different body is rejected with 422. A concurrent retry (sent while the first is still in flight) is rejected with 409 — back off briefly and retry once the first call has finished. Transient responses (5xx, 429, 408) are not cached, so you can recover by retrying.Request body
1–100 order UUIDs to cancel. Each ID is processed independently — failures on one ID do not abort the rest of the batch.
Example request
This DELETE carries a JSON body, so the signing payload’s
bodyHash is the SHA-256 hash of the body — not the empty hash used for body-less DELETEs like Cancel order.Response
Always
CLOB for batch endpoints today.Per-order outcomes, in the same order as the request.
Only CLOB orders with status
open or partial_filled can be cancelled. AMM orders execute instantly and cannot be cancelled — sell your shares to exit instead. Batch cancel charges one rate-limit token per ID.