Polygon · Rate Limits

Polygon Rate Limits

The Polygon Basic (Free) plan is hard-capped at 5 API requests per minute. Paid Stocks, Options, Indices, Forex, Crypto, and Futures plans (Starter, Developer, Advanced) advertise unlimited API requests subject to soft fair-use. WebSocket cluster connections are tier-gated; the Free plan permits a single concurrent connection per asset cluster. Throttled responses return HTTP 429 with a Retry-After header.

Polygon Rate Limits is the machine-readable rate-limit profile for Polygon on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 6 rate-limit definitions, measuring requests_per_minute, concurrent_connections, and subscribed_channels.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Fintech, Market Data, Stocks, Options, and Crypto.

6 Limits Throttle: 429
FintechMarket DataStocksOptionsCryptoForexIndicesRate Limiting

Limits

Basic (Free) REST plan api_key
requests_per_minute
5
Hard cap on Free tier across REST.
Paid plans (Starter/Developer/Advanced) api_key
requests_per_minute
-1
Advertised as unlimited; soft fair-use applies.
WebSocket connections (Free / Starter) api_key
concurrent_connections
1
Free and Starter tiers limited to a single WebSocket cluster connection per asset class.
WebSocket connections (Developer) api_key
concurrent_connections
1
Developer tier still typically capped at 1 concurrent cluster connection.
WebSocket connections (Advanced / Business) api_key
concurrent_connections
-1
Higher tiers permit multiple cluster connections.
WebSocket subscription channels per connection connection
subscribed_channels
-1
No hard documented cap; subscribers should avoid wildcard explosion (e.g. T.*) on Free tier.

Policies

Backoff Strategy
On 429, honor Retry-After and apply exponential backoff with jitter.
Connection Reuse
Reuse WebSocket connections; do not open per-message connections.
Pagination
Use next_url cursor for large result sets rather than tightening limit and re-polling.
Flat Files For Bulk
For historical bulk loads, prefer the S3-style flat files product over high-rate REST polling.

Sources