For All Markets : Deprecating the Creator Search Affiliate Trace Orders API

The Creator Search Affiliate Trace Orders API will be fully retired on <span style="color: #D83931">2026-08-15</span><span style="color: #D83931"><strong> </strong></span>; all partners must complete migration before this date to avoid integration failures. This API allowed partners to retrieve a list of affiliate orders generated by a creator, returning the order ID and product ID, so that partners could track affiliate conversions on behalf of a creator. Going forward, developers should migrate to the Search Creator Affiliate Orders API, which provides the same capability of retrieving a creator's affiliate orders for tracking affiliate conversions.

The Creator Search Affiliate Trace Orders API will be retired and replaced by the Search Creator Affiliate Orders API. The response payload remains the same; the main differences lie in the endpoint path, version, and the time-filter query parameters, as summarized below.

Endpoint

What markets & sellers are affected?

This change applies globally and affects:

• Markets: All markets where the affiliate program is available (both cross-border and local).
• Seller types: All seller types (both cross-border and local sellers).
• Affected callers: All partners and developers currently calling the Creator Search Affiliate Trace Orders API to retrieve a creator's affiliate orders.

All developers currently using the Creator Search Affiliate Trace Orders API must migrate to the Search Creator Affiliate Orders API before <span style="color: #D83931"><strong>2026-08-15</strong></span>. Failure to migrate by the sunset date will result in API call failures. The migration involves the following three steps:

1. Switch the endpoint from POST /affiliate_creator/202505/orders/trace/search to POST /affiliate_creator/202410/orders/search.
2. Replace the time_ge / time_lt / time_type parameters with create_time_ge / create_time_lt.
3. Verify that your integration correctly parses the response payload. The response fields are identical to the deprecated API — no other field differences are expected.