TikTok Shop Product API

TikTok Shop Product

Features

• Single PDP detail lookupSubmit one supported public TikTok Shop PDP URL and receive at most one normalized product record, making the endpoint suitable for enriching a known item rather than discovering products.
• Seller, price, and visible commerce signalsThe product record preserves exposed seller identity, sale and original pricing, currency, discount, rating, review count, and sold count for direct field-level evaluation.
• Media, category, and SKU contextReturned records include exposed product images with dimensions plus category and SKU or variant structures from the public product page.

Parameters

How to Use

Submit a supported product URL, save the asynchronous task ID, and read the normalized product after the task succeeds.

1. Send a POST request to /v1/tiktok-shop/product with one supported PDP url and an optional region.
2. Save the returned task_id and poll GET /v1/tasks/{task_id} until the status is succeeded or failed.
3. Read data.results.items after success and follow next_cursor only when has_more is true.

curl -X POST "https://api.socq.ai/v1/tiktok-shop/product" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://www.tiktok.com/shop/pdp/example-product/1729587769570529799","region":"US"}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items after status becomes succeeded

Best Use Cases

• Search or catalog result enrichment: Use a known PDP URL to add seller, price, rating, media, category, and SKU fields to a selected search or shop-catalog product.
• Product signal snapshot comparison: Compare collected sale price, original price, discount, rating, review count, and sold count across point-in-time product records.
• Category and variant review: Inspect exposed category, image, and SKU structures to review how a public product is organized and presented.

Pro Tips

• Validate that the input is a full tiktok.com PDP URL with a numeric product ID before submitting it to avoid a rejected request.
• Keep region set to US unless the product belongs to another accepted market, and treat a non-US empty result as a possible availability boundary.
• Do not send results_limit: one task accepts one product URL and can return at most one normalized record.
• Treat nullable seller, price, signal, media, category, and SKU fields as a public-page snapshot, and handle a succeeded task with no item without creating a placeholder product.

Related APIs