TikTok Shop API for product search and product details

The xplaai TikTok Shop API provides authenticated GET routes for product search and product details. Search accepts a query, page and region; product details accept a supported TikTok Shop URL. Returned sales figures are cumulative unless repeated snapshots establish a time-window change.

Create an API key or open the current documentation.

Choose the correct endpoint

Task Endpoint Required input
Search products GET /v1/tiktok/shop/search query
Read one product GET /v1/tiktok/product TikTok Shop url

Search also accepts a page and two-letter region. The current product-detail contract is US-focused, and non-US search results may be less stable. Design the interface so users can see the selected region instead of assuming global coverage.

Search for products

export XPLA_API_KEY="your_api_key"

curl --get 'https://xplaai.com/v1/tiktok/shop/search' \
  --header "Authorization: Bearer $XPLA_API_KEY" \
  --data-urlencode 'query=portable blender' \
  --data-urlencode 'page=1' \
  --data-urlencode 'region=US'

Validate queries before sending them. The documented search contract trims the query, limits its length and validates page and region values.

Retrieve product details

The product route expects a supported HTTPS TikTok Shop product link. A successful response may include title, description, images, price, currency, promotion information, cumulative sales, rating, reviews, video, seller information, product identifiers and inventory signals.

Fields depend on the public product and current source response. Do not invent missing values or silently replace them with estimates.

Cumulative sales are not seven-day sales

The search endpoint does not expose a strict date-window parameter. A field returned as sales should therefore be described as cumulative sales.

To calculate a change:

  1. store the product identifier and first value;
  2. record the collection timestamp;
  3. collect the same field later;
  4. subtract only comparable values;
  5. label the result as a snapshot difference, not guaranteed demand.

For an Agent-managed process that stores candidates in Lark or Feishu, use the TikTok Shop product research tool.

Build API logic or use a Skill

Use the API when your application owns queries, storage, scoring and review. Use xplaai Commerce Skills when Codex or WorkBuddy should follow a packaged research process.

Return to the unified AI API for other developer endpoints.

Frequently asked questions

Which TikTok Shop API endpoints are available?

Use /v1/tiktok/shop/search for search and /v1/tiktok/product for one supported product link.

Which region should I use?

Use a documented two-letter region. The current product-detail route is limited to US, and other search regions may be less stable.

Is the sales field a seven-day growth figure?

No. Treat it as cumulative unless your system compares consistent snapshots collected at different times.

Which product URLs work?

Use supported TikTok Shop HTTPS product paths. Invalid or unrelated URLs should be rejected before a data request.

Does xplaai fill missing product fields?

No. Product fields depend on the current public data response; unknown values should remain unknown.

When should I use the research Skill?

Use it when Codex or WorkBuddy should organize candidates, evidence and later snapshots in a repeatable workflow.

Start with one narrow query

Create an API key, search one US category term and inspect the returned fields before building filters or automated scoring.