Etsy · Rate Limits

Etsy Rate Limits

Etsy Open API v3 publishes application-based rate limits applied at the API key level for both public-auth and private-auth requests. Each Application receives a per-second (QPS) allowance and a 24-hour sliding-window per-day (QPD) allowance. The defaults documented in the developer portal example are 10 requests per second and 10,000 requests per day for new commercial apps; the publicly cited example in the rate limits documentation shows higher allowances (QPS 150, QPD 100,000) for apps that have been upgraded. Per-application limits can be raised by emailing developer@etsy.com with the application description and projected usage. Limits apply to every API key uniformly — there is no separate sandbox/test-mode tier.

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

It captures 5 rate-limit definitions, measuring requests_per_second, requests_per_day, and varies.

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

Tagged areas include Rate Limiting, Marketplace, Open API v3, Throttling, and Quotas.

5 Limits Throttle: 429 Quota: 429
Rate LimitingMarketplaceOpen API v3ThrottlingQuotas

Limits

Per-Second Requests (Default Commercial App) key
requests_per_second · second
10
Default QPS allowance for a newly approved commercial application (Application tier). Visible in the Developer Portal under "Your Apps."
Per-Day Requests (Default Commercial App) key
requests_per_day · day
10000
Default 24-hour sliding-window quota for a newly approved commercial application. Visible in the Developer Portal.
Per-Second Requests (Documented Upgraded Example) key
requests_per_second · second
150
Example QPS allowance shown in the Etsy rate limits documentation; reflects an upgraded application that has requested higher capacity.
Per-Day Requests (Documented Upgraded Example) key
requests_per_day · day
100000
Example QPD allowance shown in the Etsy rate limits documentation; reflects an upgraded application that has requested higher capacity.
Per-Application Custom Limits key
varies
application-specific; visible in the Etsy Developer Portal
Each Application has its own per-second and per-day limits set by Etsy. Limit headers on responses (x-limit-per-second, x-limit-per-day) reflect the actual numbers in force for the API key making the call.

Policies

HTTP 429 + Retry-After
When either the per-second or per-day allowance is exhausted, Etsy returns HTTP 429 with a retry-after header indicating how long to wait before retrying. Clients MUST respect this header.
Exponential Backoff
Etsy recommends exponential backoff when 429s persist. Use the retry-after value as a floor for the wait time.
Pre-emptive Throttling via Headers
Every 2xx response includes x-limit-per-second, x-remaining-this-second, x-limit-per-day, and x-remaining-today. Clients can throttle before hitting the limit by watching the remaining counters.
Application-Scoped, Not User-Scoped
Rate limits are applied at the API key level and shared across all OAuth users of the application. There is no per-user uplift; OAuth users consume the application's bucket.
Limit Upgrades via Support
Upgrades to higher per-second / per-day allowances are granted by Etsy on request. Email developer@etsy.com with the application name, a description of the integration, and the expected request volume.
Single-Bucket Across Environments
Etsy does not publish a sandbox or test-mode tier with relaxed limits. Live production calls and development calls draw from the same per-application bucket.

Sources