Get TikTok video details by video ID
View all TikTok Profiles, Videos & Sounds API endpoints →Retrieve details for one TikTok video using its video_id path parameter. Supply the numeric video identifier as a string, rather than a username or a full video URL. The documented default is 7468030505628224790; it is an example input, not a promise of continued video availability. No pagination or request-body input is documented for this lookup. Observed success metadata reports status equal to ok, data.status_code equal to 0, and a data.aweme_detail object containing aweme_id, author.unique_id and create_time. The observed video had aweme_id 7697307919943060767 and author.unique_id khaby.lame, with create_time 1792169181. Its description, 9500-millisecond video duration, music information and engagement statistics were also observed. These observations describe a successful lookup, not a guaranteed response for every identifier. No source response example is supplied. The available evidence does not enumerate the description, duration, music or engagement subfields, establish the exact music identifier property, or guarantee playable media URLs. Confirm those nested fields in the returned object before implementing extraction or chaining a music lookup. Keep video identifiers as strings to avoid numeric precision loss. Treat engagement values as a retrieval-time snapshot, and record your own fetched_at time separately from create_time. Video metadata does not confer download or reuse rights, provide private-account access, or replace official creator analytics.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/tiktok/video-data API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tiktok/video-data?key=<API_KEY>&video_id=7468030505628224790'
Query Result
Use Cases
- Enrich a selected TikTok feed video ID with its detail record and observed creator attribution while preserving the identifier as a string throughout storage and joins.
- Compare a small set of clips using creation timestamps, available descriptions and duration information, recording a separate fetched_at value for each detail lookup.
- Inspect a video's returned music information to obtain a sound identifier for a separate music lookup, confirming the identifier property before building that connection.
- Capture available video-level engagement counters at scheduled intervals to build a snapshot history, checking the returned counter fields instead of assuming a fixed statistics schema.
Frequently asked questions
Should video_id contain a TikTok URL or just the video identifier?
Provide only the video identifier as a string in the path. The documented default and placeholder are 7468030505628224790. A full TikTok URL or username is not the documented input format, and long identifiers should not be converted to precision-limited numbers.
Which video-detail fields have actually been observed?
The successful probe metadata reports status equal to ok, data.status_code equal to 0, and data.aweme_detail with aweme_id, author.unique_id and create_time. Description text, a 9500-millisecond video duration, music information and engagement statistics were also observed, but their nested field names were not enumerated. No source response example is supplied to establish a complete schema.
Was the documented default video ID the one used in the successful probe?
No. The documented default is 7468030505628224790, while the successful probe returned video 7697307919943060767 with author.unique_id khaby.lame and create_time 1792169181. The successful observation should not be treated as validation of the default video's current availability.
Can I get a sound ID from the video's music information?
Music information was observed in the video details, so it can support a video-to-sound workflow when it includes an identifier. The evidence does not establish that identifier's exact property name. Inspect the returned music object before extracting an ID for a separate music lookup; do not assume every video includes usable music information.
Do engagement statistics represent historical or official creator analytics?
No. Treat available engagement values as a snapshot of the retrieved video, not a complete history or an official creator analytics report. Record your own fetched_at time for each lookup separately from the video's create_time and verify the actual counter fields before storing comparisons.
Does this lookup guarantee a permanent playable video URL?
No. The available evidence does not guarantee playable media URLs or their lifetime. Retrieving metadata does not grant download, redistribution or reuse rights.