来自 TikTok Shop 官方资料快照 ·
- 当前资料结构化阅读页
- 固定快照已留存,可追溯
- 官方原文可核对
资料正文
§1 Create your app in Partner Center
Creating an app in Partner Center establishes the workspace and credentials you need to integrate with TikTok Shop services. In this workspace, you choose the app type, service category, market, seller type, API scopes, redirect URL, webhook settings, and app credentials. This guide covers the full app creation flow and the decision between Public app and Custom app. For the OAuth-only setup flow, use Create a TikTok Shop app OAuth client. That page should focus on the OAuth client configuration: redirect URL, authorization link, authorization code, token exchange, and refresh-token handling.
§2 Before you create an app
Complete this checklist before clicking Create app & service:
| Check | Why it matters |
|---|---|
| Developer account and onboarding are complete or in progress | Partner Center app creation depends on your developer account status and developer type. See Developer onboarding. |
| Developer type is clear | ISVs, seller developers, system integrators, and partners can follow different review and launch paths. |
| App type is clear | Choose Public app if sellers should discover the app in the App and Service Store. Choose Custom app if the app is distributed privately by authorization link. |
| Service category is clear | Category affects available scopes, review expectations, and app positioning. Connector apps may have additional review requirements. |
| Target market and seller type are confirmed | Treat Market and Seller type as creation-time choices. They may not be editable after app creation, so confirm them before creating the app. |
| Redirect URL is ready | Needed to receive the authorization code after a seller or partner authorizes your app. Use a secure backend-controlled endpoint. |
| Webhook URL is ready, if needed | Needed to receive push notifications for order, product, fulfillment, authorization, and other events. |
| Compliance and legal review path is understood | Review requirements vary by app type, category, market, and data access. US and UK partners should start compliance/legal review early because it can take three or more weeks. |
§3 App type decision
There are two main app types: public and custom.
| Item | Public app | Custom app |
|---|---|---|
| Visibility | Listed in the TikTok Shop App and Service Store after approval. Sellers can discover, install, and authorize it. | Not listed publicly. Developers share a private authorization link with selected sellers. |
| Typical use case | SaaS or integration app intended for many sellers. | Seller-specific or partner-managed solution, often built for one seller or a limited seller group. |
| App listing details | Required for store listing. | Usually not required unless Partner Center requests them. |
| Distribution | App and Service Store listing. | Private authorization link. |
| Review standard | Public apps require app review before listing. | Custom apps usually launch privately without public-app listing review, but app review is required if the app is a Connector app, reaches 25 or more seller authorizations, or Partner Center / your partner manager indicates review is required for the selected category or market. |
Standard wording to reuse across related docs:
Custom apps usually launch privately by authorization link. App review is required only for applicable custom apps, such as Connector apps, custom apps with 25 or more seller authorizations, or apps in a category or market where Partner Center requests review.
§4 Connector and 25-seller review rule
A Connector app is an app category for integrations that connect TikTok Shop with an external system, such as an ecommerce platform, ERP, OMS, WMS, 3PL, feed tool, or other seller operation system. Connector apps typically sync product, order, inventory, fulfillment, or other seller data across systems, so TikTok Shop may require review even if the app is distributed privately. For custom apps:
- If the app category is Connector, prepare for app review.
- If the app reaches 25 or more seller authorizations, prepare for app review before broader use.
- If Partner Center shows a review-required status, review banner, publish restriction, or Submission materials for review entry, follow that flow before expanding distribution.
- If you believe the app is below the threshold but still sees a review requirement, contact your partner manager or submit a Partner Center support ticket with the app key, service ID, app category, market, seller type, and screenshots.
§5 Create the app
To create your app:
- Sign in to the correct Partner Center for the target market.
- Open App & Service from the navigation panel.
- Click Create app & service.
- Select Public or Custom.
- Select the Service category and set the default name.
- Optionally upload a logo.
- Select Market and Seller type.
- Turn on Enable API if the app will call TikTok Shop APIs.
- Configure the redirect URL and webhook URL.
- Click Create.
Field reference:
| Field | Meaning | Notes |
|---|---|---|
| App type | Public or Custom. | Choose based on how sellers will discover and authorize the app. |
| Service category | The business category of the app, such as Connector or another category shown in Partner Center. | Category can affect available scopes, review requirements, and launch flow. |
| Default name | The default app/service name shown in Partner Center and used as fallback display text. | Public apps may need localized listing content later. |
| Logo | App icon or logo. | Optional during initial creation, but public listings usually require polished brand assets. |
| Market | The market where the app will operate or be listed. | Confirm before creation. If the market is wrong and Partner Center does not allow editing, create a new app or contact support. |
| Seller type | Seller model supported by the app. | Local usually means local-to-local seller/shop scenarios. Cross-border means cross-border seller scenarios and may require additional identifiers such as shop_cipher or global product flows. |
| Enable API | Turns on API integration setup for the app. | Enable this if the app needs OpenAPI scopes, seller authorization, token exchange, or webhooks. |
| Redirect URL | Callback endpoint that receives the authorization code. | The token API uses the returned code value as the auth_code parameter. |
| Webhook URL | Callback endpoint that receives event notifications. | You can also manage shop webhooks later through Events API and Partner Center webhook settings. |
§7 App credentials
After creation, Partner Center displays the app or service detail page. You can find the app credentials later from:
Partner Center
-> App & Service
-> Select your app or service
-> App credentials / Basic information
| Credential | Meaning | Handling requirement |
|---|---|---|
| App Key | Public identifier of the app/service. | Used in token requests and signed OpenAPI requests. |
| App Secret | Secret key generated for the app/service. | Store only on the server side. Use it for token exchange and request signing. Do not expose it to browsers, mobile apps, client-side scripts, screenshots, or logs. |
| Service ID | Identifier used by some authorization-link flows. | Use it when building authorization links manually or when Partner Center asks for service-level identification. |
§9 Document boundaries
Use these pages together, but keep their responsibilities separate:
| Page | Owns | Does not own |
|---|---|---|
| Create your App | App type selection, app creation fields, market/seller type choice, credentials, and high-level review rules. | Detailed OAuth callback implementation or token refresh logic. |
| Create a TikTok Shop app OAuth client | OAuth client setup, redirect URL behavior, authorization code handling, token exchange, and refresh-token flow. | Public vs custom app strategy or app launch review path. |
| App development overview | End-to-end development lifecycle: design, create, test, review, launch. | Field-by-field app creation instructions. |
| App launch overview | Publish and launch path for public and custom apps. | Initial app creation details. |
| App review process | Review materials, review workflow, and review status. | OAuth token exchange or API signing. |
§10 Next steps
After creating the app:
- Configure required API scopes in Partner Center.
- Configure and test the Redirect URL.
- Configure webhook topics if the app relies on event notifications.
- Generate a test authorization code and exchange it for tokens.
- Call Get Authorized Shops to confirm the token and shop mapping.
- Test with Development Shop and API Testing Tool.
- Follow the applicable launch or review path for the app type, category, market, and seller authorization scale.
