GET
/orders-scoringGet scoring status for multiple orders
Checks if multiple orders are currently scoring for rewards. An order is considered "scoring" if it meets all the criteria for earning maker rewards: - The order is live on a rewards-eligible market - The order meets the minimum size requirements - The order is within the valid spread range - The order has been live for the required duration
- Base URL
- https://clob.polymarket.com
- Auth
- L2 API credentials (key, secret, passphrase)POLY_API_KEY, POLY_ADDRESS, POLY_SIGNATURE, POLY_PASSPHRASE, POLY_TIMESTAMP
- Rate limit
- 9,000 req / 10s (900 per second)
- Limit applies to
- CLOB API general
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| order_ids | query | string[] | yes | Array of order IDs (order hashes) to check scoring status for |
Example
curl -X GET "https://clob.polymarket.com/orders-scoring?order_ids=<order_ids>" \
-H "POLY_API_KEY: $POLY_API_KEY" \
-H "POLY_ADDRESS: $POLY_ADDRESS" \
-H "POLY_SIGNATURE: $POLY_SIGNATURE" \
-H "POLY_PASSPHRASE: $POLY_PASSPHRASE" \
-H "POLY_TIMESTAMP: $POLY_TIMESTAMP"L2 requests are signed with HMAC-SHA256 using your API secret, and the timestamp is part of the signature, so keep the machine's clock accurate. A missing credential or a stale signature both come back as Unauthorized/Invalid api key. The Python SDK signs for you.
Responses
| Status | Meaning |
|---|---|
| 200 | Successfully retrieved scoring status for all orders |
| 400 | Bad request - Invalid payload or order ID |
| 401 | Unauthorized - Invalid API key or authentication failed |
| 500 | Internal server error |
| 503 | Service unavailable - Trading disabled |
Related endpoints
- POST /orders-scoring CLOB API
From Polymarket's published OpenAPI spec and rate-limit tables, synced 2026-10-04.