OpenSea · Rate Limits
Opensea Rate Limits
OpenSea REST and Stream API rate limits. Three separate buckets apply to read, write, and fulfillment operations. Instant free-tier keys are limited to 2 creations per hour per IP and expire after 30 days.
Opensea Rate Limits is the machine-readable rate-limit profile for OpenSea on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests_per_minute and keys_per_hour.
The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Rate Limiting, API Management, and NFT.
4 Limits
Throttle: 429
Rate LimitingAPI ManagementNFT
Limits
Read (Free / Instant Tier) api_key
60
Write (Free / Instant Tier) api_key
5
Fulfillment (Free / Instant Tier) api_key
5
Instant Key Creation ip
2
Policies
Three separate rate limit buckets
Read, write, and fulfillment requests are tracked independently with their own per-minute limits.
Instant keys expire after 30 days
Keys generated via POST /api/v2/auth/keys are valid for 30 days. Permanent keys are available via opensea.io/settings/developer.
Backend-only usage recommended
API keys should never be exposed in client-side/frontend code. Use a backend wrapper to securely store and proxy requests.
Cross-chain support
The same API key works across all supported chains including ethereum, polygon, base, arbitrum, optimism, solana, and 20+ others.