TikTok Shop Customer Service API Approval: Eligibility Checklist for 2026
TikTok Shop’s Customer Service API is a custom, approved scope—not a general TikTok DM API. TikTok’s current documentation asks applicants to show a working in-app chat, Order, Fulfillment, and After-Sales integrations, and either 1,000 authorized sellers or 1 million API calls per day. A self-developed TikTok Shop Seller app may receive special approval, but seller authorization is still required before shop data can be accessed.
Key takeaways
- The Customer Service API is for TikTok Shop buyer-to-seller conversations. It does not expose every direct message received by an ordinary TikTok account.
- Approval starts with product evidence: a live chat interface, conversation history, and operational order, shipping, return, and refund context.
- TikTok’s published scale gate is 1,000 authorized sellers or 1 million API calls per day; a self-developed merchant app can be considered for special approval.
- Approval of the custom scope and authorization by each seller are separate gates. Your app needs both before it can read that shop’s conversations.
- If the actual requirement is ordinary-account inbound messaging rather than TikTok Shop buyer support, evaluate that as a separate architecture decision.
Who can apply for TikTok Shop Customer Service API access?
TikTok describes the Customer Service API as a custom API for independent software vendors and merchants building their own support tools. In Partner Center, the partner or ISV selects Customer Service as both the business category and the app or service category, then requests access to the custom scope.
The official Customer Service API overview lists four practical approval layers:
| Approval layer | Evidence TikTok asks for | Why it matters |
|---|---|---|
| Working support product | A user-visible chat window, conversation list and detail, timestamps, participants, and a real send-and-receive flow | The API is meant to extend an existing support product, not serve as the first component of a prototype |
| Commerce context | Order, Fulfillment, and After-Sales surfaces linked to the conversation | Agents must be able to see order status, shipment progress, returns, and refunds while helping a buyer |
| Partner scale | At least 1,000 authorized sellers or 1 million API calls per day | Customer Service is a restricted custom scope rather than a default API category |
| Authorization | The app receives the custom scope and each seller authorizes access | Scope approval does not grant access to every shop automatically |
TikTok says an app in the TikTok Shop Seller category—meaning a merchant with its own development team—may receive special approval. Treat that as a review path, not a guaranteed exemption. The official page does not promise approval merely because one merchant owns the app.
This is the key distinction from the broader tiktok dm api question. The general TikTok developer platform still does not provide a live inbox endpoint for an ordinary account. The Shop Customer Service API is a narrow, reviewed path for commerce conversations between buyers and sellers.
What the approved scope actually provides
After approval and seller authorization, the official API can list conversations, retrieve messages, send and mark messages as read, manage agent settings, upload buyer-message images, and receive New Conversation and New Message webhooks. TikTok’s reference documents the required scope as seller.customer_service.
For example, the official Get Conversation Messages operation uses:
GET /customer_service/202309/conversations/{conversation_id}/messages
Required scope: seller.customer_serviceThat endpoint belongs to TikTok Shop and requires a seller access token. It is not interchangeable with TikTok for Developers’ Login Kit, Content Posting, Research, or Data Portability products. The existing TikTok commerce API capability map explains that wider product boundary; this checklist focuses only on obtaining the restricted Customer Service scope.
Application evidence checklist
Prepare the review package before requesting the custom scope:
- Show the full chat product. Capture an uncropped conversation list and detail view, participant identity, timestamps, history, and the send-and-receive flow. TikTok asks for screenshots plus a short screen recording; a mockup may not prove that the product is operational.
- Connect conversations to commerce data. Show order details, delivery status, and the relevant return or refund state, plus how an agent uses them during a live conversation.
- Prove the scale gate you rely on. Show 1,000 authorized sellers or reporting that demonstrates 1 million API calls per day. A self-developed Seller app should explain the merchant, development team, and internal support workflow instead of assuming an automatic exception.
- Request the correct custom scope. TikTok’s access-scope guide says custom scopes must be requested in Partner Console → App & Service → Manage → Manage API. Confirm that
seller.customer_serviceis enabled for the app. - Test seller authorization separately. A successful app review is not a seller token. Verify installation and authorization, store the shop identifier and granted scope, and handle revocation.
- Recheck the official page before submission. Custom-scope rules can change by market and account. This article records the documentation visible on July 18, 2026; Partner Center is the final source for the application presented to your account.
Decide which messaging surface you actually need
| Your requirement | Correct surface | Main constraint |
|---|---|---|
| Support TikTok Shop buyers inside an existing commerce helpdesk | TikTok Shop Customer Service API | Custom-scope review, product evidence, scale, and seller authorization |
| Send approved commerce outreach to eligible past buyers | TikTok Shop Customer Engagement API | Separate feature permissions, recipient eligibility, templates, and frequency rules |
| Export a user’s authorized TikTok data | TikTok Data Portability API | Review, supported region, user consent, and export—not a live inbox |
| Receive supported inbound messages from a connected ordinary account | UnifyPort unofficial interface | Separate account connection and webhook operating model; no TikTok Shop privileges |
Run this decision before writing code. A team that needs order-linked Shop conversations should pursue the official Customer Service API. A team that needs a general account’s live inbound stream should not build Order and Fulfillment screens merely to make a different product look eligible.
Where UnifyPort fits
UnifyPort does not grant seller.customer_service, approve a Partner Center app, authorize shops, expose Seller Center order data, or supply TikTok’s official agent and service metrics. Use the official API when those commerce capabilities are requirements.
UnifyPort fits the separate ordinary-account inbound case. The UnifyPort Exporter release guide documents the browser-assisted TikTok session handoff, while the API delivers supported inbound traffic through the standard message.received webhook envelope. A hypothetical inbound event uses the same documented fields as other providers:
{
"id": "evt_7b9f2d41c6",
"type": "message.received",
"provider": "tiktok",
"account_id": "acc_4e81a7",
"occurred_at": "2026-07-18T03:14:25Z",
"data": {
"conversation": { "id": "7421183065", "type": "user" },
"sender": { "id": "7369021841", "type": "user", "name": "Mina" },
"message": {
"id": "msg_20260718_031425",
"type": "text",
"text": "Is this item available in Thailand?",
"direction": "inbound",
"sent_at": "2026-07-18T03:14:24Z"
}
}
}When the webhook endpoint has a signing_secret, verify X-Device-Timestamp and X-Device-Signature against the raw body before storing the event. The standard event types and payload reference is the deepest source for the envelope; check the current provider capability documentation before depending on any outbound action.
Limitations and trade-offs
The official TikTok Shop path is the better fit when agents need Shop buyer identity, order linkage, conversation lifecycle, approved outbound behavior, or native service operations. It keeps commerce authorization and platform policy inside TikTok’s supported model.
The unofficial interface cannot make an app eligible for the Customer Service API, convert ordinary DMs into Shop conversations, start official buyer campaigns, or reproduce Seller Center data. Its narrower value is a standard inbound event stream for supported connected accounts. Keep order and fulfillment records in your own system only when you already have a lawful, reliable source for them.
FAQ
What are the TikTok Shop Customer Service API approval requirements?
TikTok currently asks for a working in-app chat window, visible Order, Fulfillment, and After-Sales integrations, and either 1,000 authorized sellers or 1 million API calls per day. The app must request the custom Customer Service scope, and each seller must authorize access.
Can a single TikTok Shop merchant get Customer Service API access?
Possibly, but not automatically. TikTok says a self-developed app in the TikTok Shop Seller category may receive special approval. The merchant should submit evidence of its development team, operational chat product, commerce context, and intended support workflow.
Is the Customer Service API a general TikTok DM API?
No. It covers TikTok Shop buyer-to-seller customer-service conversations. It does not expose every DM received by a creator or ordinary TikTok account.
Does app approval remove the need for seller authorization?
No. Custom-scope approval makes the capability available to the app; seller authorization grants that app access to a specific shop. Both gates must be satisfied.
What should I do if my app does not qualify?
Keep the requirement precise. Use Seller Center for official Shop support, finish the missing product evidence before reapplying, or evaluate an ordinary-account inbound interface if Shop-only identity, order, and agent capabilities are not actually needed.
Next step
If your product truly owns Shop buyer support, use TikTok’s Customer Service API overview as the application checklist and confirm the requirements inside your Partner Center account. If your requirement is ordinary-account inbound routing, review UnifyPort’s standard webhook event reference before choosing the separate connection path.
Sources
Official TikTok sources checked on July 18, 2026: