TikTok Shop: server-level public app and App Store installs

Chiusa
  • Qualcosa non va?
#1,533 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@helpcodeai ci sta già lavorando.

Dal 5/11/2026.

  • #1535 di @helpcodeai — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
typescript
Ambito
authentication, backend

Direzione di ricerca

Read the TikTok Shop connector and OAuth callback flow, then inspect the setup page and server configuration for existing app credentials. Trace how authorization state and workspace connector creation work before assessing the proposed install flow. Done means supporting server-level app credentials, setup behavior, and App Store installs in both cloud and self-hosted modes; linked pull request #1535 is already open.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Follow-up to #1522 / #1523.

Why

Most TikTok Shop sellers cannot create their own Partner Center app: TikTok only lets sellers with an assigned account manager register as seller developers. So the TikTok Shop connector, which today needs the seller's own App key, App secret and Service ID, works only for a few sellers.

A server can register one public TikTok Shop app (an ISV app in the TikTok Shop App Store) and let every seller authorize that app. TikTok reviews such an app before it is listed, and its reviewers install it from the App Store. That install sends the seller to our Redirect URL with a code but without a state we issued, which the callback refuses today.

Proposal

  1. Server app. New optional server variables: TIKTOK_SHOP_PLATFORM_APP_KEY, TIKTOK_SHOP_PLATFORM_APP_SECRET and TIKTOK_SHOP_PLATFORM_SERVICE_ID.
    • When they are set and a TikTok Shop connector leaves its own App key empty, the connector signs, authorizes and renews with the server app.
    • A connector that has its own App key keeps using it, as today.
    • The server secret is never written to a connector and never shown in the dashboard.
  2. Setup. When the server app is available, the setup page does not ask for App key, App secret or Service ID. The seller can still enter their own app.
  3. Store-initiated install. When the callback has a code but no state we issued, and the server app is configured, it does the following:
    • it stores a single-use install record;
    • it forwards the seller to the dashboard, where they sign in or sign up;
    • it adds a TikTok Shop connector to their workspace, or reuses one that still waits for authorization;
    • it exchanges the code with the server app.

Cloud and self-hosted

The behaviour is identical in both modes and depends only on the server variables.

  • Self-hosted: with the variables unset, nothing changes.
  • Cloud: sets them to the AnythingMCP app.
Lingua principale
TypeScript
Stelle
856
Fork
82
Merge medio
5h 58m
PR unite (30g)
457

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di HelpCode-ai/anythingmcp

Tutte le issue di HelpCode-ai/anythingmcp

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.