Rate-limits
The Depop API applies rate limits to ensure fair usage and maintain performance. The allowance for each group of endpoints is currently the same for every integration.
- You are a direct partner if you manage your own shop, or a small number of shops you own, using an API key for each shop.
- You are a cross-lister if you provide a service used by many Depop sellers, who each connect their shop to your application with OAuth 2.0.
What is different for each kind of integration
| Direct partners | Cross-listers | |
|---|---|---|
| What the endpoint allowances apply to | Each shop you hold an API key for | Each seller connected to your application |
| A limit on your application as a whole | None. Your per-shop allowances are the only limits you hit. | Yes. 30,000 requests per minute across every seller and endpoint combined. |
| The limit you are most likely to hit | The create/full-update allowance, during a bulk relist | The application-wide limit, once you have many connected sellers |
The endpoint allowances and the 429 response are the
same for both. Cross-listers also need to read the application-wide limit.
Limits for each shop or seller
Every shop (if you are a direct partner) or connected seller (if you are a cross-lister) has its own allowance for each group of endpoints. Requests you make for one shop or seller never use up another's allowance.
| Endpoint group | Endpoints | Limit for each shop or seller |
|---|---|---|
| Create or fully update a listing | POST /api/v1/products/PUT /api/v1/products/by-sku/{sku}/PUT /api/v1/products/by-product-id/{productId}/PUT /api/v1/products/by-slug/{slug}/ |
200 requests per 10 seconds (≈ 20 per second) |
| Live insights | GET /api/v1/insights/shop/live/GET /api/v1/insights/products/.../live/ |
600 requests per 5 minutes (≈ 2 per second) |
| Everything else | All other endpoints, including getting, patching and deleting products, mark-as-sold, offers, orders, shipping, refunds, seller details, pricing inspiration and webhook configuration | 6,000 requests per minute (≈ 100 per second) |
Each row is a separate allowance. The "everything else" allowance is shared across every endpoint in that row, so for example 3,000 order lookups and 3,000 product patches for the same shop or seller in one minute would use up its whole allowance.
Cross-listers only: a limit on your application as a whole
As a cross-lister, every request you make, for any seller and any endpoint, also counts towards a single allowance for your application:
| Scope | Limit |
|---|---|
| All requests made by your application, for every seller and every endpoint combined | 30,000 requests per minute (≈ 500 per second) |
This allowance does not grow as you connect more sellers, and it is the limit you are most likely to hit.
Staying within each seller's limits is not enough
100 sellers each making 5 requests per second is 500 requests per second for your application, which is the whole allowance, even though every one of those sellers is comfortably within their own limits. Throttle the total request rate across all sellers, not just the rate per seller.
Staying within your limits
- Pace creates and full updates, and prefer
PATCHfor small changes. The create/full-update allowance is the smallest, and a bulk relist or full catalogue push is the quickest way to exhaust it. Pace those jobs to 20 requests per second for each shop or seller, and usePATCHfor anything that is not a new listing or a complete rewrite: partial updates come out of the much larger "everything else" allowance. - Use webhooks instead of polling. Webhooks tell you about sales, refunds and product changes as they happen, so you do not need to poll the orders or products endpoints on a schedule.
Need higher limits?
The default limits are suitable for most integrations. If your use case needs more, contact us through the Depop portal or at [email protected] describing your expected request volumes, why you need them, and how you plan to use them. Specific limits may be agreed as part of your partner terms.