Skip to main content

​
APIs

The Perps API is available over HTTP and WebSocket, with public market data and authenticated trading and account operations on both.

HTTP API

https://api.perpetuals.polymarket.comMake request-response calls for market data, trading, and account management.

WebSocket API

wss://ws.perpetuals.polymarket.com/v1/wsStream public and private updates, or send trading actions over a persistent connection.

​
Before You Integrate

Authentication

Set up credentials for private HTTP and WebSocket access.

Rate Limits

Review request, trading action, and WebSocket limits.

Geographic Restrictions

Check where Perps order placement is available.

​
Correlate Requests with Exchange Logs

Every HTTP response the exchange produces — including errors and overload responses — carries an x-pmp-pod header identifying the gateway pod that produced it. WebSocket handshake responses carry the same header, on both the successful 101 upgrade and handshake rejections. Record it with your request logs so your traffic can be matched against exchange logs when you work with support. The value is the gateway pod name, or a hexadecimal process instance ID when the pod name is unavailable. It is correlation metadata only: pods are not addressable, and a cached response keeps the identity of the pod that originally produced it. Responses to malformed HTTP carry no header. Browsers can read the header through CORS, but browser WebSocket APIs do not expose handshake headers — authenticated WebSocket sessions instead receive the pod identity in the successful auth acknowledgement, described in Authenticated Sessions. Treat the header and the field as optional: responses from older pods omit them during a rolling deploy.