快工助手跨境电商知识与商机助手

For All Markets: Sandbox Shops Rate Limiting & Inactive Seller Access Control

TikTok Shop 官方资料 · TikTok Shop Partner Center 开发者文档 · 适合开发者

stable本次发布有变化全部展示

来自 TikTok Shop 官方资料快照 ·

打开官方原文 ↗
  1. 当前资料结构化阅读页
  2. 固定快照已留存,可追溯
  3. 官方原文可核对
查看技术与溯源信息
平台 / profile
TikTok Shop / profile.tiktok.docs_api
语言
en-US
发布版本
cn-20260909-2
标签
zhuge/sourceplatform/tiktok_shopaudience/developercategory/api_doctopic/compliancetopic/developer

资料正文

§1 1. Overview

To improve platform data security and ensure fair use of the Open API, the API Gateway will introduce two new control policies:

  1. Sandbox shop rate limiting — all sandbox shops will be subject to a unified QPH limit of 1000.
  2. Inactive seller/shop access control — Open API requests from shops or sellers in inactive states will be rejected.

Both changes apply at the API Gateway layer and affect how ISV integrations behave under the listed conditions.

#

§2 2. What Is Changing

#

§3 1 、 Sandbox User QPH Rate Limiting

1 、 Sandbox User QPH Rate Limiting

  • Policy: Requests from sandbox shops are now rate-limited on a per-hour basis. The unified limit is QPH = 1000 (1000 requests per hour per sandbox user).
  • Scope: Applies to sandbox shops only. Production shops are not affected by this sandbox limit.

Behavior on exceeding the limit:

HTTP status429
error_code36009037
error_messageToo many requests. Current sandbox user made too many requests in a short period of time.
#

§4 2、Inactive Seller / Shop Access Control

2、Inactive Seller / Shop Access Control

Effective date — 2026-07-20. The inactive seller / shop access control policy will take effect on 2026-07-20. From this date, Open API requests on behalf of shops/sellers in blocked states (DEACTIVATED, REJECTED, WITHDRAW, CLOSING) will be rejected. ISVs should complete the required handling before this date.

The Gateway will validate the shop/seller status on each Open API request. Only the following statuses are allowed to access the Open API; all other statuses are blocked.

AccessStatuses
✅ AllowedNEW_CREATE, PENDING, ACTIVE
❌ BlockedDEACTIVATED, REJECTED, WITHDRAW, CLOSING
#

§5 2.1 Error responses

2.1 Error responses

ScenarioHTTP statuserror_codeerror_message
Shop inactive40136009043Your shop has been deactivated or is closing. Access denied.
Seller inactive40136009044Your seller account has been deactivated. Access denied.
#

§6 3. Impact & Affected Parties

3. Impact & Affected Parties

Who is affected

  • ISVs using sandbox / test users for any traffic beyond legitimate testing → will hit the QPH limit (429 / 36009037).
  • ISVs whose integrations call the Open API on behalf of shops/sellers in inactive states (DEACTIVATED / REJECTED / WITHDRAW / CLOSING) → those requests will be rejected (401 / 36009043 / 36009044).

Nature of change

  • These are Gateway-level access policies. Requests from active, properly-authorized sellers using production users within the limit are unaffected.
#

§7 4. Required Actions for ISVs

  1. Keep sandbox / test user traffic within QPH = 1000; do not use sandbox users for production-scale or data-scraping workloads.
  2. Add handling for the new error responses: 429 + 36009037 → sandbox rate limit exceeded, apply back-off and retry after the hourly reset; 401 + 36009043 / 36009044 → shop/seller is inactive, stop calling the Open API for that shop/seller and prompt the merchant to resolve their account status.
  3. Review integrations to confirm they only call the Open API for shops/sellers in allowed statuses (NEW_CREATE, PENDING, ACTIVE).
#