Skip to main content
POST
/
api
/
orders
/
cancel-batch
Cancel a batch of orders by id (max 100)
curl --request POST \
  --url https://core-api.adipredictstreet.com/api/orders/cancel-batch \
  --header 'Content-Type: application/json' \
  --header 'X-Api-Key: <api-key>' \
  --data '
{
  "orderIds": [
    "<string>"
  ]
}
'
{
  "cancelled": [
    "<string>"
  ],
  "notCancelled": {}
}

Authorizations

X-Api-Key
string
header
required

Partner / integrator key — format ps_live_<keyId>_<secret>. Issued by PredictStreet ops on request; never self-service. Never ship to a browser. multi_wallet partners must additionally send X-User-Wallet: 0x<40-hex> on every authenticated request to declare the acting wallet. See the API keys guide for scope taxonomy, partner kinds, rate limits, and rotation procedure.

Headers

X-User-Wallet
string

Required for multi_wallet partners on every authenticated request; ignored for single_wallet. Declares the acting end-user wallet for this request — drives KYC checks, balances/positions/orders attribution, rate-limit buckets, and audit. Lower-cased server-side. Missing on a multi_wallet key → 401 api_key_user_wallet_required; malformed → 401 api_key_user_wallet_invalid. The on-chain CTFExchange/Vault contracts still verify EIP-712 signer ↔ vault binding, so loosening API-layer attribution is safe by construction.

Pattern: ^0x[a-fA-F0-9]{40}$
Example:

"0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb3"

Body

application/json
orderIds
string[]
required

1–100 server-side order ids (UUIDs). Duplicates are de-duplicated server-side.

Required array length: 1 - 100 elements

Response

Per-id outcome split into cancelled and notCancelled.

cancelled
string[]
required

Ids of the orders that transitioned to CANCELLED.

notCancelled
object
required

Map of orderId → reason for every id that was not cancelled. Reasons: not_found (unknown id, or an order owned by another wallet — no existence leak), already_terminal (already CANCELLED / FILLED / REJECTED / EXPIRED — idempotent), lock_invariant (a per-order balance-lock invariant tripped; the rest of the batch is unaffected), unknown (transient failure — safe to retry).