Using public (api key-based) authentication, clients are allowed 10,000 requests per 24-hour period, with a limit of 10 queries per second. We use a progressive rate limit structure, where a 24 hour period is chunked into 12 two-hour blocks. Rate limits are calculated by summing the number of requests made per two-hour block over the past 24 hours. This is to maximize your use of the API - for example, if you hit a rate limit, you'll only need to wait for at most two more hours in order to get a few more allowed requests (the exact amount will depend on the number of requests you made in the two-hour block of 24 hours prior). Using private (OAuth) authentication, clients are given the same limits per OAuth access token.
If your application needs more than the allotted number of calls, contact us at firstname.lastname@example.org with a description of the application and an estimate on needed call usage. You might also want to investigate the use of caching to keep the number of calls to a minimum, and make your application more responsive.
Headers: Every API response bears rate limit headers, as described below:
X-Limit-Per-Secondis the total limit of calls an app API key can make to the Etsy API per second.
X-Remaining-This-Secondis the remaining number of call an app API Key can make in the current second.
X-Limit-Per-Dayis the total limit of calls an app API key can make to the Etsy API per day.
X-Remaining-Todayis the remaining number of call an app API Key can make in the current day.
Note: When a rate limit has been reached, a return response code of
429 is returned and none of the above headers will return.
These default rate limits are subject to change at any time, without notice.