stable本次发布有变化全部展示
来自 TikTok Shop 官方资料快照 ·
- 当前资料结构化阅读页
- 固定快照已留存，可追溯
- 官方原文可核对
资料正文
§1 1. Overview
Today, when an ISV creates a target (open) collaboration, it calls Create Open Collaboration directly and only learns the outcome from the response. Because the creation endpoint enforces a set of business rules (including conflicts with existing target collaborations on the same creator + product), creation frequently fails, forcing ISVs into a trial-and-error loop and putting unnecessary load on the creation API. To address this, the Affiliate category has released two new APIs that introduce a “pre-check → resolve → create” pattern:
- Check Target Collaboration Conflicts (202605) — a pre-check endpoint that detects whether the target creator/product combination has conflicting collaborations and whether they can be terminated.
- Cancel Target Collaboration Conflicts (202605) — a conflict-resolution endpoint that terminates the resolvable conflicts so creation can proceed.
This lets ISVs validate before they create, dramatically reducing failed Create Open Collaboration calls.
§2 2. Recommended Call Flow
New best-practice flow: Pre-check first, resolve if needed, then create.
- Call Check Target Collaboration Conflicts with the target creators and products.
- If conflicts exist → call Cancel Target Collaboration Conflicts to resolve the conflict items, then call Create Open Collaboration.
- If no conflicts exist → call Create Open Collaboration directly.
Image
§3 3. New APIs
#§4 3.1 Check Target Collaboration Conflicts (202605)
3.1 Check Target Collaboration Conflicts (202605)
| Method & Path | POST /affiliate_seller/202605/target_collaborations/conflicts/check |
|---|---|
| Purpose | Retrieve conflicting target collaborations for the product and determine if they can be terminated. |
| Key request body | creator_open_id_list — creator open ID list; product_id_list — product ID list |
| Response | Standard wrapper code, message, request_id, data (conflict details indicating which items conflict and whether they are resolvable). |
§5 3.2 Cancel Target Collaboration Conflicts (202605)
3.2 Cancel Target Collaboration Conflicts (202605)
| Method & Path | POST /affiliate_seller/202605/target_collaborations/conflicts/resolve |
|---|---|
| Purpose | Execute resolution actions on resolvable conflict items within the scope of seller authorization. |
| Key request body | conflict_items — list of user and product identifiers with target collaboration conflicts that caused creation failure. |
| Response | Standard wrapper code, message, request_id, data (resolution result per conflict item). |
§6 4. Impact & Affected Parties
4. Impact & Affected Parties
- Who is affected: All ISVs / developers that create target (open) collaborations via Create Open Collaboration, especially those currently retrying on creation failures.
- Nature of change: This is additive — no breaking change. Create Open Collaboration continues to work as-is; the two new endpoints are an optional but strongly recommended pre-flight + remediation step.
- Benefit: Fewer failed creation calls, clearer failure reasons before creation, and lower load on the creation endpoint.
§7 5. Required / Recommended Actions for ISVs
- Integrate Check Target Collaboration Conflicts before every Create Open Collaboration call to detect conflicts up front.
- When conflicts are returned and resolvable, call Cancel Target Collaboration Conflicts to terminate them, then proceed to create.
- When no conflicts are returned, call Create Open Collaboration directly.
- Update error-handling logic to rely on the pre-check result instead of trial-and-error against the creation endpoint.