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

Cerrado
  • ¿Algo no está bien?
#1,533 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@helpcodeai ya está trabajando en esto.

Desde el 5/11/2026.

  • #1535 de @helpcodeai — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
typescript
Área
authentication, backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
TypeScript
Estrellas
856
Forks
82
Merge medio
5 h 58 min
PR fusionados (30 d)
457

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de HelpCode-ai/anythingmcp

Todos los issues de HelpCode-ai/anythingmcp

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.