GET
/auth/ban-status/closed-onlyGet closed-only mode status
Retrieves the closed-only trading mode status for the authenticated user. When closed-only mode is enabled, the user can only close existing positions and cannot open new ones.
- 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
Example
curl -X GET "https://clob.polymarket.com/auth/ban-status/closed-only" \
-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.
Response fields
| Field | Type | Description |
|---|---|---|
| closed_only | boolean | Whether the user is in closed-only trading mode |
Responses
| Status | Meaning |
|---|---|
| 200 | Successfully retrieved closed-only mode status |
| 401 | Unauthorized - Invalid API key or authentication failed |
| 404 | Not found - No ban status record found for the address |
| 500 | Internal server error |
Related endpoints
- POST /auth/api-key CLOB API
- DELETE /auth/api-key CLOB API
- GET /auth/api-keys CLOB API
- GET /auth/derive-api-key CLOB API
- GET /auth/builder-api-key CLOB API
- POST /auth/builder-api-key CLOB API
From Polymarket's published OpenAPI spec and rate-limit tables, synced 2026-10-04.