TikTok Live Data
The TikTok live endpoints return normalized profile and video data. The API can reuse recent source data, so usescraped_at to assess when each result was collected.
Endpoints
One credit is $0.01. See Pricing for billing and payment-rail rules.
The listed credit price applies to each successful response, including one that reuses recent source data.
Fetch a profile
Pass a bare username or include the leading@.
List profile videos
next_cursor back as cursor while has_more is true. Each request returns the complete source page. Cursors are opaque, so store and return the value unchanged.
Each video has a stable video_id, canonical TikTok URL, author, description, timestamps, engagement counts, hashtags, music metadata, and media fields. Slideshows use media_type: "slideshow" and place image URLs in images.
Fetch one video and its file URL
Pass the TikTok URL as a query parameter.data.video.video_url contains a directly downloadable media URL when the source exposes one. The URL is signed and temporary. Download the file promptly instead of storing the URL for later use. video_url is null when no downloadable video stream is available, including slideshow-only posts.
Fetch comments
next_cursor for the next source page.
video_id can be null when a short share URL returns an empty comment page and the source does
not provide the resolved video ID.
Fetch a transcript
source is captions or generated, and language reports the detected language. The detected-language transcript is reused on later requests. Every delivered transcript costs five credits, including a reused response.
Transcript generation can run for up to 180 seconds. Set a timeout of at least 190 seconds when you call this endpoint with a custom HTTP client. The generated Influship SDK uses a 210-second default timeout.
URL and retry rules
Video-level endpoints accept HTTPS URLs ontiktok.com and its subdomains, including vm.tiktok.com and vt.tiktok.com. Other hosts return 400 validation_error before the source request runs.
Retry
503 responses with bounded exponential backoff and jitter. Do not retry 400, 404, or 422 without changing the request or source URL.
Payment rails
The endpoints accept API keys, OAuth, x402, and MPP when those payment methods are enabled. API-key and OAuth requests are charged for successful operations. x402 and MPP use the advertised request price once payment settles, including when the final endpoint response is an error. A successful x402 settlement returns aPAYMENT-RESPONSE header, while MPP returns a Payment-Receipt. See x402 and MPP before choosing a no-key rail.