快工助手跨境电商知识与商机助手

Call supported developer APIs

TikTok Shop 官方资料 · TikTok Shop Partner Center 开发者文档 · 适合开发者

stable本次发布有变化全部展示

来自 TikTok Shop 官方资料快照 ·

打开官方原文 ↗
  1. 当前资料结构化阅读页
  2. 固定快照已留存,可追溯
  3. 官方原文可核对
查看技术与溯源信息
平台 / profile
TikTok Shop / profile.tiktok.docs_api
语言
en-US
发布版本
cn-20260909-2
标签
zhuge/sourceplatform/tiktok_shopaudience/developercategory/api_doctopic/compliancetopic/developer

资料正文

§1 Call supported developer APIs

The devapi command group exposes fixed OAuth-backed methods for supported Partner Center and Developer Center operations. It does not accept an arbitrary caller-provided path.

#

§2 Discover the installed method catalog

tts_open_toolkit auth login
tts_open_toolkit devapi list --json

Always use the installed CLI as the source of truth for method names and accepted inputs.

#

§3 Call a method

tts_open_toolkit devapi call partner-profile --json
tts_open_toolkit devapi call developer-app-detail --query app_key=<app_key> --json
tts_open_toolkit devapi call partner-service-detail --query service_id=<service_id> --query locale=en-US --json
#

§4 Published fixed methods

MethodPurpose
account-basic-infoRead basic developer-account information.
account-certification-infoRead account certification information.
developer-app-listList developer Apps, optionally filtered by keyword.
developer-app-detailRead one App by required app_key.
developer-app-existsCheck whether a developer App exists.
document-api-metaRead API-document metadata by source document ID.
authorization-open-api-listRead authorized OpenAPI items for a package and optional App.
sandbox-shop-listList sandbox shops.
sandbox-account-listList sandbox accounts with supported filters.
partner-service-listList partner services.
partner-profileRead the active partner profile.
partner-service-detailRead one partner service by service ID.
open-app-listList open Apps with pagination and filters.
#

§5 Use JSON for automation

  • Use --json when an agent or script consumes the response.
  • Preserve safe error text, HTTP status, and request or log IDs for diagnosis.
  • Do not parse human-readable output when JSON is available.
  • Secret-bearing response fields are recursively removed. Public identifiers such as app_key remain available.

💡 Prefer fixed devapi call methods. Use auth request only for an explicit diagnostic against a known existing route, never to bypass an allowlist.


#

§6 Was this page helpful?

Was this page helpful?

Tell us what worked, what was unclear, or what should be added. TTS Open Toolkit Feedback Form

#