来自 TikTok Shop 官方资料快照 ·
- 当前资料结构化阅读页
- 固定快照已留存，可追溯
- 官方原文可核对
资料正文
§1 MX market: GS POP API Updates
#§2 Summary
Summary
We're rolling out some updates to our Product, Fulfillment, and Return and Refund APIs in order to better support our Global Selling Platform Open Plan (GS POP) in the Mexico (MX) market.
§3 Impact
Impact
| Impacted market(s) | * Mexico (MX-CB) |
| Impacted version(s) | * 202309 (and later) |
§4 Changes
Changes
§5 Product APIs
Product APIs
§6 Product listing rules
Product listing rules
To list GS POP products for MX, call POST Create Global Product first, then publish to local shops (this is the same workflow as GS POP for other markets).
Field value validation:
- Product title:
[1, 300]characters - Product price range (oversea local warehouse):
[1, 50000] - Product price range (oversea direct mail):
[1, 4560]
| Endpoint(s) | Change(s) |
|---|---|
| * GET Global Categories | * Returns the category tree information for MX market * Added es-MX as a possible value for the locale parameter |
| * GET Global Category Rules * GET Global Attributes | * Support using MX market category ID to retrieve category and attribute rules * Added es-MX as a possible value for the locale parameter |
| * POST Recommend Global Categories | * product_title should be within [1, 300] characters |
| * POST Create Global Product * PUT Edit Global Product | * product_title should be within [1, 300] characters * Max SKUs: 100 |
| * POST Publish Global Product | * publish_target.region: Added MX as a possible region value * skus.price.currency: Added MXN as a possible currency value |
§7 Fulfillment APIs
Fulfillment APIs
§8 Fulfillment workflow
Fulfillment workflow
For MX GS POP orders, apps need to evaluate whether the order needs to be split first. Image
- Call GET Order Detail or POST Get Order List to retrieve order details.
- Call GET Order Split Attributes to evaluate whether the order must be split (
must_split=true), and obtain split rules (must_split_reasons) if so. - Call POST Split Orders to split the order into multiple packages. Obtain the
package_idandsplittable_group_idfrom the API response. For MX GS POP orders, you must split the order to meet the required conditions in a single API call. - Call POST Ship Package or POST Batch Ship Packages using the
package_idfrom the previous step.
| Endpoint(s) | Change(s) |
|---|---|
| * GET Order Split Attributes | Added the following new parameters: * must_split: Indicates whether the order needs to be split * must_split_reasons: Limitations on the maximum number of items per package and category-specific item quantity limits * must_split_reasons.type * must_split_reasons.category_id * must_split_reasons.max_count |
| * POST Split Orders | Added error code 21003002: Split order failed due to platform limitations. Use the Get Order Split Attributes endpoint to find out the exact reason |
| * POST Ship Package * POST Batch Ship Packages | Added error code 21004024: Ship order failed due to platform limitations. Use the Split Orders endpoint to split the order before attempting to ship |
§9 Return and Refund APIs
Return and Refund APIs
§10 Cancel reasons
Cancel reasons
For order cancellations initiated by MX sellers, the available cancel reasons are different. Compared to other markets, the following options are not supported as cancel reasons for sellers in Mexico:
- Pricing error -
seller_cancel_unpaid_reason_wrong_price - For local shops, if the cancellation reason is already in use, it must be discontinued to avoid potential issues.
When order is in UNPAID, ON_HOLD, or AWAITING_SHIPMENT, supported cancel reasons are:
UNPAID:
- Out of stock:
seller_cancel_unpaid_reason_out_of_stock - Buyer did not pay on time:
seller_cancel_unpaid_reason_buyer_hasnt_paid_within_time_allowed - Buyer requested cancellation:
seller_cancel_unpaid_reason_buyer_requested_cancellation
ON_HOLD and AWAITING_SHIPMENT:
- Out of stock:
seller_cancel_reason_out_of_stock - Unable to deliver to buyer address:
seller_cancel_paid_reason_address_not_deliver - Buyer requested cancellation:
seller_cancel_paid_reason_buyer_requested_cancellation