The job we are building toward
Developers should be able to submit a public TikTok video URL and receive a transcript, language, timestamps when available, and a stable source status. A useful contract also needs predictable authentication, quotas, rate limits, idempotency, structured errors, and a clear rule that failed work is not charged.
Tell us the volume and reliability you actually need
A generic waitlist does not help define an API. Early-access requests should state the daily or monthly request volume, workflow, latency tolerance, required fields, retry behavior, callback needs, and willingness to pay for completed requests. These inputs determine the first useful API surface and its operating economics.
Candidate workflows
- Creator or brand monitoring over a known list of public video URLs
- Transcript ingestion for RAG, search, classification, and research systems
- Batch campaign analysis with source-linked Hook, Problem, Solution, Proof, and CTA fields
- Automation that turns completed transcripts into briefs, captions, or review queues
What early access will not promise
Public availability does not remove platform restrictions. Private, deleted, region-blocked, age-restricted, photo-only, silent, or provider-blocked posts may remain unavailable. Early access will not claim universal coverage, perfect accuracy, fixed latency, or production SLA until those properties are measured.
Frequently asked questions
Is the ReelTranscript public API available now?
Not yet. This page collects concrete early-access demand while the public authentication, quota, error, reliability, and billing contract is being prepared.
What should I include in an early-access request?
Describe the workflow, expected requests per day or month, whether you need polling or callbacks, required output fields, acceptable latency, and whether failed requests must be unbilled.
Which videos would the API support?
The intended scope is publicly accessible individual TikTok videos. Private, removed, restricted, photo-only, silent, or provider-blocked posts cannot be promised as successful inputs.

