来自 TikTok Shop 官方资料快照 ·
- 当前资料结构化阅读页
- 固定快照已留存，可追溯
- 官方原文可核对
资料正文
§1 2026 August TikTok Shop API Updates Summary
Below is a summary of TikTok Shop Open API updates for August 2026. One of these updates is a Breaking Change (Sell Across EU: Global Product APIs migrating to the Local Replication architecture), and a series of category-level mandatory attribute, certification, and size chart requirements will take effect starting in September. Please prioritize impact assessment and complete the required migrations and field updates according to each market's effective date. Severity markers used in this document: 🔴 [Breaking] means your integration stops working unless you migrate. ⚠️ [Action Required] means the API stays compatible, but products, orders, or labels can fail if you do not adapt.
For the full record, refer to the Changelog at the end of this document.
§2 1. Breaking Changes and Key Updates
1. Breaking Changes and Key Updates
| Update | Required Actions | Key Date |
|---|---|---|
| ⚠️ [Action Required] US 4PL Express Shipping Is Now Live Eligible US 4PL orders may now return an Express option (initially UPS 2nd Day Air) in addition to Standard shipping. No new API version, order status, scope, or required request field is introduced. | · Process every item in shipping_services; do not assume a single service. · Remove any hardcoded shipping_service_id; always pass the ID returned for that order. · Do not route on the exact service display name. · Note the restrictions: Express does not support dangerous goods or P.O. box destinations, and Collection by TikTok does not provide Express pickup. | Live since August 12, 2026 |
⚠️ [Action Required] SEA In-Store Pickup: Order and Fulfillment API Changes Get Order Detail / Get Order List add instore_pickup_sla_time and a new delivery_option_name enum In-store Pickup. Update Package Delivery Status adds a verification_code request field (pickup OTP) and uses delivery_type = DELIVERY_SUCCESS. Ship Package / Batch Ship Packages now confirm shipment and notify the buyer that the order is ready for pickup. New error codes: 21042248 / 21042247 / 21042252 (Update Package Delivery Status) and 21042251 (Ship Package, Batch Ship Packages). | · Parse the new response field and enum, and support the verification_code submission flow. · Handle the new error codes, including the retry-after-30-minutes and incorrect-code cases. · Adapt the In-Store Pickup order status semantics: IN_TRANSIT = awaiting OTP verification, DELIVERED = picked up and verified; PARTIALLY_SHIPPING and AWAITING_COLLECTION do not apply. · Note that recipient phone_number and name are desensitized. · Applies to local-to-local sellers in SG, PH, VN, TH, ID, MY, all API versions. | Effective September 1, 2026 |
| ⚠️ [Action Required] Structured Size Chart Capabilities OpenAPI capabilities for creating, managing, parsing, and validating structured size charts are being enhanced (Search Size Charts, Create / Edit Size Chart, Get Category Rule measurement requirements, Parse Size Chart Image, and size-chart quality checks). TikTok Shop will progressively introduce governance for products in applicable categories that do not provide a qualified size chart. | · Support at least one submission method — recommended: create or reuse a structured template and submit size_chart.template.id; alternatively upload an image via Upload Product Image with use_case=SIZE_CHART_IMAGE and submit size_chart.image.uri. · Use Get Category Rule to confirm whether a size chart is supported or required for the category. · Ensure a qualified size chart: covers every size on sale, uses one consistent size and unit system, lists sizes in clear order without duplicates, includes category-relevant key measurements, and uses valid values. | Expected availability September 4, 2026 |
| ⚠️ [Action Required] Thailand TIS Requirements for Slime & Squishy Toys and Stress Relief Toys The TIS certificate mark on the product label becomes a mandatory qualification for these two categories, and TIS Standard Number and TIS License Number change from optional to mandatory attributes. | · Use Get Category Rules to confirm mandatory certification requirements and Get Attributes to confirm mandatory attributes. · Write the TIS certificate mark into the certifications parameter of Create / Edit / Partial Edit Product. · Applies to local-to-local and POP sellers in Thailand, all API versions; without it, products cannot be created or updated. | Effective September 15, 2026 |
| ⚠️ [Action Required] EU Product Attribute Changes and New Category Openings Seven updates in total. Four attribute collection or mandatory-field adjustments: Recommended Age / Material Feature / Electrical Product (toys, maternity & baby); Power Mode / Contains Batteries or Cells? (Electronics, EEE); Model / Batch Number becoming mandatory (Electronics, EEE, Textile); and the EU GARAN guarantee attributes (voluntary durability guarantee of at least 2 years, Guarantee Duration, Producer Name, Model Identifier). Plus three new category openings: Household Cleaners / CLP / Biocides (IE, ES, IT, FR), Solar Panels (EU), and Pre-owned Luxury Watches (IT). | · Use Get Attributes to add the new and newly mandatory fields to listing, editing, bulk import, and API submission, and validate them before submission. · Use Get Categories to refresh the category list for the newly opened categories. · Update product templates, internal SOPs, and support scripts so frontline teams know which fields must be populated. | GARAN attributes enforced September 28, 2026; other attribute items enforced October 1, 2026 |
🔴 [Breaking] EU Sell Across EU: Global Product APIs (GPA) Migrating to Local Replication The Sell Across EU product model moves from the legacy GPA model (GLOBAL_PUBLISHING, GPID as the cross-market identifier, Create / Publish / Edit / Partial Edit Global Product) to the Local Replication architecture (LOCAL_REPLICATION, one PID per shop, Create Product / Replicate Product / Edit or Partial Edit Product / Bind Local Products, with asynchronous replication tracked via webhook). | · Review whether your integration still uses GPA for Sell Across EU and plan the migration before the deprecation date. · Rework product creation, product mapping, and webhook handling logic; replication is asynchronous, so state must be driven by webhook. · Build all new EU integrations directly on the Local Replication architecture. | Legacy GPA deprecated by October 30, 2026 |
⚠️ [Action Required] Indonesia Mandatory Attribute "Imported Goods" The attribute "Imported Goods" (Attribute ID 102254, values Yes = 1000058 / No = 1000059) becomes mandatory for all categories except the digital category. | · Use Get Attributes to confirm mandatory attributes and pass the value through Create Product, Edit Product, and Partial Edit Product. · Applies to local-to-local sellers in Indonesia, all API versions; without it, products cannot be created or updated. | Effective October 27, 2026 |
§3 2. Featured New Capabilities (Highly Recommended)
2. Featured New Capabilities (Highly Recommended)
The platform introduced two capability sets this month, covering affiliate operations automation and returns decision management. Both reduce operating and integration costs while allowing partners to move from manual, page-by-page work to programmable workflows. Priority review is recommended.
§4 2.1 Affiliate Seller APIs Upgraded: 6 New APIs Plus 4 Enhanced Endpoints
2.1 Affiliate Seller APIs Upgraded: 6 New APIs Plus 4 Enhanced Endpoints
Six new Affiliate seller APIs are released and four existing endpoints are upgraded, covering outreach quota, creator promotion performance, and IM inbox management.
- Check quota before outreach:
Get Weekly Creator Outreach Quotareturns the shop's GMV tier, quota used and remaining, and the follower cap, so bulk outreach no longer fails as a whole when quota runs out. - Collect outreach results afterwards:
Get Weekly Creator Outreach Recordsreturns paginated records withhas_sent_im_message→has_sent_invitation→is_paired, which supports deduplication and funnel measurement. - Product-level promotion performance:
Query Creator Promotion Details in Target Collaborationreturns commission rate, promotion video count, and promotion LIVE count per product inside one target collaboration. - IM inbox management:
Update Conversation Statusstars, unstars, or archives a conversation;Get Inbox Category Countsfeeds all inbox badges in one call. - Richer IM messages:
Send IM MessageaddsCRM_TEXT_WITH_IMAGE_CARDandCRM_TEXT_WITH_PRODUCTS_CARD(up to 5 products);Get Conversation Listadds theconversation_statusfilter (ALL/UNREAD/UNREPLIED/STARRED/ARCHIVED). - Target collaboration:
Create Target Collaborationadds the optionalpreferred_content_type(LIVE/VIDEO);Search Target Collaborationsaddscreate_timeplus keyword search by product or invitation. - Bug fix:
Upload Message Image V2fixes the issue where images uploaded by US cross-border sellers through the previous version were not accessible to creators.
Integration notes: available in all markets and for all seller types, across versions 202412 / 202508 / 202607 / 202608. All changes are backward compatible — only optional request fields, new response fields, and new enum values are added, no new permission scope is introduced, and already-authorized apps do not need to be re-authorized. Recommended for: all sellers and ISVs running affiliate creator outreach, target collaborations, or affiliate IM.
§5 2.2 Get Review Decisions API for US & EMEA
2.2 Get Review Decisions API for US & EMEA
A new Get Review Decisions API lets sellers evaluate which seller decisions are currently allowed for a specified aftersales request, returning one result per requested decision together with whether it is currently eligible and, for an eligible reject decision, the applicable rejection reasons.
The key difference from the legacy Get Decisions Eligibility API is the query parameter return_or_cancel_id. Sellers can keep using the SKU-level TTS return_id, or pass the batch return parent RMA id to receive every sku_id from the buyer's original return submission in a single payload, with eligible decisions broken out per return_line_item_id. This removes the multiple calls previously required for each SKU-level return_id when a buyer returns several SKUs at once.
Integration notes: this is not a breaking change. Apps that already hold the Return & Refund Basic scopes do not need new authorization, and existing Get Decisions Eligibility integrations continue to work. There is no plan to deprecate the legacy API this year, and any sunset plan will be announced separately — but new development should use Get Review Decisions.
Recommended for: apps and partners in the US, EU, and UK markets that manage returns and aftersales decisions.
§6 3. Other Updates
3. Other Updates
| API Category | Update Summary | Details |
|---|---|---|
| Product API | Get Product v202309 adds not_submitted_reasons | GET /product/202309/products/{product_id} adds data.audit.not_submitted_reasons (List<String>) to explain why a product has not been submitted for audit. It is populated only when audit.status=NONE and unmet shop listing prerequisites block submission; otherwise it returns []. Possible values: PAYMENT_ACCOUNT_NOT_LINKED, SHOP_INACTIVE, and W8_NOT_CONFIGURED (US shops only). Additive change — apps with strict response schemas should update their models, support multiple values, and tolerate future unknown values, while continuing to treat audit.status as the source of truth. |
| Product API | Recommend Category accepts optional source-platform product context | POST /product/202309/categories/recommend adds five optional request fields: origin_platform_product_type, origin_platform_vendor, origin_platform_tags, origin_platform_category (id / name / full_name / is_leaf / is_root), and origin_platform_product_meta_data.attribute_value_list[] (name / values). Designed for catalog synchronization and cross-platform listing integrations. Fully additive — existing payloads remain valid, and no action is required if you do not send source-platform context. |
| Order API | Temporary listings identifiable in Order APIs (all markets) | Get Order List (POST /order/202309/orders/search) and Get Order Detail (GET /order/202309/orders, GET /order/202507/orders) return data.orders[].line_items[].product_listing_type, with value TEMPORARY_LISTING. This lets order management, shipping, and WMS apps route temporary listing SKUs to a separate shipping workflow. Response-only and non-breaking; apps must tolerate other values and a missing field and must not fail order ingestion. Available in all markets since July 30, 2026. |
| Fulfillment API | Japan customs information APIs (v202607) | Two new endpoints — Get Order Customs Requirements (POST /fulfillment/202607/orders/customs_info/query) and Upload Customs Information (POST /fulfillment/202607/orders/customs_info/submit) — add a conditional customs step between order retrieval and package fulfillment. Query first, then judge by need_fill_clearance and already_filled_clearance: when a submission is required, map order_line_id, sku_id, qty, and price_percent (integer percentage) and submit before creating or shipping the package. Existing order and package API schemas are unchanged, and no migration of existing endpoints is needed. Error codes to handle: 11001002 (fix the request, do not retry unchanged), 11001012 / 11001027 / 11001001 (retry with exponential backoff). Effective July 24, 2026. |
| Fulfillment API | US warehouse_id in Get Package Detail | GET /fulfillment/202309/packages/{package_id} adds data.warehouse_id (String), identifying the warehouse associated with a package's actual fulfillment, including cases where TikTok Shop switches the fulfillment warehouse after the order is placed. This resolves warehouse-level inventory reconciliation discrepancies after a warehouse switch. No request change; store the value as a string rather than a number and treat the field as optional. |
§7 References
References
- Changelog: https://partner.tiktokshop.com/docv2/changelog
- API Documentation: https://partner.tiktokshop.com/docv2/
If you have any questions about the updates above or need support, please submit a ticket to contact us. Thank you.