This documentation is specific to Polymarket US. The international version can be found here.
Streaming First Architecture
| Use Case | Recommended API |
|---|---|
| Real-time market data | gRPC Market Data Stream |
| Real-time order/trade updates | gRPC Order Stream |
| Order entry/cancellation | REST Trading API |
| Historical data queries | REST Report API |
| Account management | REST Accounts API |
| KYC and payments | REST Partner APIs |
Base URLs
| Environment | Base URL |
|---|---|
| Development | https://api.dev01.polymarketexchange.com |
| Pre-production | https://api.preprod.polymarketexchange.com |
| Production | https://api.prod.polymarketexchange.com |
/v1/ path prefix.
Authentication
All API requests require an access token in theAuthorization header:
API Groups
Trading APIs
For direct trading operations. Used by all partners.| Endpoint Group | Description | Streaming Alternative |
|---|---|---|
| Trading | Insert, cancel, and replace orders | - |
| Report | Search orders and trades, download history | Order Stream |
| Positions | Query account balances and positions | - |
| Reference Data | List instruments, symbols, and metadata | - |
| Order Book | Get order book depth and best bid/offer | Market Data Stream |
| Drop Copy | Execution feed and trade capture | Order Stream |
Partner APIs
For partners building retail trading platforms with end-user onboarding, KYC, and payments.Partner Guide
Complete guide for partners including Accounts, KYC, and Payments APIs
Which APIs do I need?
- Direct trading partners: Use the Trading APIs documented in this section
- Retail partners: Use Trading APIs plus the Partner Guide APIs
Request Format
Headers
| Header | Required | Description |
|---|---|---|
Authorization | Yes | Bearer {access_token} |
Content-Type | Yes | application/json |
x-participant-id | Conditional | Your participant ID (required for trading, positions, and report endpoints) |
When is
x-participant-id required?- Required for all account-scoped endpoints: trading, positions, reports, and account operations
- Not required for market data, order book, reference data, and instrument state endpoints
GET /v1/accounts/whoami to see your firm identity, or GET /v1/accounts/users to list all users and their IDs. See Accounts & Identity for details.Request Body
POST requests accept JSON bodies:Response Format
Success Response
Error Response
| HTTP Status | Meaning |
|---|---|
200 | Success |
400 | Bad Request - Invalid parameters |
401 | Unauthorized - Invalid or expired token |
403 | Forbidden - Insufficient permissions |
404 | Not Found - Resource doesnβt exist |
429 | Too Many Requests - Rate limited |
500 | Internal Server Error |
Price Representation
All prices are represented asint64 values. Divide by the instrumentβs price_scale to get the decimal price:
Query price_scale from the Reference Data API and cache it for each instrument.
Rate Limits
Trading endpoints are rate-limited at 250 requests per second per firm, averaged over a 1-minute window (short bursts above this rate are allowed). Query endpoints have lower per-endpoint limits. Public (unauthenticated) endpoints are limited to 20 requests per second per IP. See Rate Limits for the full breakdown by endpoint and protocol.Support
For REST API questions or issues, contact onboarding@qcex.com.Next Steps
Quickstart Guide
Place your first order in 5 minutes
Authentication
Set up Private Key JWT authentication
gRPC Streaming
Real-time market data and order updates
Environments
API endpoints for dev, preprod, and prod