Managed gateway
One REST call returns typed JSON for videos, profiles, feeds, search, Tako AI, LIVE rooms, series and Shop product pages. We handle signing, contexts, retries and decoding.
How a call runs
Each call runs on a LeanPool device context with city-level egress: it is signed as the current app build (android · tiktok · 47.6.3), sent, retried on a fresh context if needed, then decoded from protobuf to JSON and billed. Every step shows up in the request trace in Logs.
Upstream paths
Every endpoint documents the mobile API path or paths it calls, such as /aweme/v2/comment/list/ for GET /v1/video/comments. Local primitives say so (local · signer), and gateway features name the gateway component. The catalog lists them all.
Resource paths and old aliases
Endpoints are grouped by resource: /v1/video, /v1/user, /v1/feed, /v1/search, /v1/shop, /v1/live, /v1/account and /v1/devices. Older paths such as /v1/scrape/comments and /v1/tools/no-watermark keep working as aliases, and each reference page lists them.
Choosing the client
Gateway reads accept optional os, app_flavour and app_version to run as a specific app build, plus region and city for egress. Leave them out to use the default. See Clients and versions.
At volume
Queue up to 500 tasks per job with batch jobs (Growth and Scale).