List user orders (Polysimulator-shape — see also: /v1/data/orders for PM-shape).
Returns the user’s pending, filled, and cancelled orders in the Polysimulator envelope: {orders, has_more, next_cursor, total_hint} with snake_case row fields (order_id, market_id, limit_price, quantity, ISO timestamps).
SDK consumers ported from Polymarket should call GET /v1/data/orders (operationId listOrdersPmShape) instead — that endpoint emits PM’s exact envelope shape ({limit, count, next_cursor, data}) and per-row schema (id, market, asset_id, original_size, size_matched, price, unix-int created_at, ORDER_STATUS_* enum). This endpoint stays live for back-compat but PM-SDK auto-generation should target the /data/orders shape.
Both endpoints read from the same underlying pending_orders table — the only difference is response shape.
Authorizations
Issue from /v1/keys (or admin-issued for enterprise tier).
Headers
Your PolySimulator API key
Polymarket-CLOB-compat alias for X-API-Key (underscore form). SDK clients ported from Polymarket can authenticate without changing header names. X-API-Key takes precedence when both are provided.
PM-CLOB-compat: Authorization: Bearer ps_live_... (or ps_test_...) is accepted as an alias for X-API-Key so py-clob-client and other ported SDKs authenticate without header name changes. Bearer JWTs are NOT accepted here — use the dashboard-auth endpoints for those.
Query Parameters
"PENDING"
Alias for cursor — PM-ported paginators pass the previous response's next_cursor back under this name (py-clob-client convention). cursor wins when both are present.