Rate limits
Understand per-endpoint limits and handle 429 responses
Rate limits are enforced per API key (or IP address if unauthenticated). Limits reset on a rolling 1-minute window.
Limits by endpoint category
429 response
When you exceed a limit, the API returns 429 Too Many Requests with a Retry-After header indicating how many seconds to wait.
The Retry-After header and retry_after body field both contain the number of seconds remaining in the current window. The body field is an RFC 9457 extension member — agents can read it without parsing headers.
Handling 429s in Python
Bulk operations
There are no batch endpoints. If you need to create many listings programmatically, throttle your requests to stay within the 120/minute limit — roughly 2 per second with headroom.
Next steps
- Idempotency — retry failed requests safely
- Errors — full error format reference