Rate Limit

Overview

The SellerCenter REST API limits how many requests each seller can send. These limits protect the platform and keep response times stable for every seller, so design your integration to use as few requests as possible.

Request Rate Limit

Each seller can send up to 30 requests per second to the SellerCenter REST API.

Note:

• The limit is counted per seller, so all applications and access tokens of the same seller share it
• Requests above the limit are rejected with HTTP status 429 Too Many Requests

Bulk Background Operations Limit

Bulk background operations have a daily limit of 50000 + 5 * number of your products rows per day.

Example: If you have 100 products, you can upload files with a maximum of 50,500 rows per day.

How to Avoid Hitting the Rate Limit

• Avoid unnecessary requests: For example, there is no need to request the list of your orders every second. Request it once per minute if you have many new orders, or once per hour if you only get a few orders per day.
• Use webhooks instead of polling: Instead of requesting an order every minute to check whether its status changed, implement a webhook and receive a callback when the order status changes.
• Cache data that rarely changes: Data such as the list of brands, the category tree, and attribute options changes very infrequently. Cache it on your side to reduce the number of calls to these endpoints.
• Send only real updates: If you changed the price of one product, do not upload the whole catalog or send price updates for all products. If nothing changed, do not send an update at all. For example, instead of pushing a stock update for all products once per hour, push it only for the products whose stock changed.
• Store the IDs returned by SellerCenter: Object IDs never change. After you create a product, save its ID on your side, so that later stock or price updates can use it directly without extra GET requests to look it up.