Douyin E-Commerce Data Assistant

The Problem

When integrating Douyin e-commerce APIs, the hard part is usually not writing requests, but untangling the permission chain: enterprise qualification, shop authorization, client_key / client_secret, OAuth access_token, scope, and API data levels often intersect. Orders, refunds, products, and logistics have separate fields, and influencer or advertising data from the Douyin ecosystem cannot always be reused from shop APIs. This skill is aimed at engineers preparing to integrate with Douyin Open Platform or Douyin Shop Open Platform, and helps identify whether the blocker is authorization, app configuration, or API scope.

How It Works

• Confirm the goal first: decide whether the requirement belongs to order.*, refund.*, product.*, logistics.*, or influencer/advertising data, instead of debugging unrelated permission domains.
• Check credentials next: verify enterprise onboarding, shop authorization, client_key / client_secret setup, whether the access_token is expired, and whether scope is sufficient.
• Troubleshoot by protocol: trace auth, rate limits, and error codes across Douyin Open Platform and Douyin Shop APIs, such as unauthorized shop, expired token, or insufficient permission.

Boundaries and Notes

This skill is meant for querying or integrating data from the user's own shop or authorized accounts only; it does not fetch unauthorized data. client_secret and access_token should remain local and not be transmitted. It provides integration guidance and a calling skeleton, rather than holding credentials or making live API calls on the user's behalf. Order and live-stream data may contain user privacy, so masking, minimization, and compliant storage are required. Final API fields, permission levels, and rate-limit rules follow the official Douyin Open Platform documentation.