Use TikTok Sound Lookup: Metadata & Videos Using It with Python
Look up any TikTok sound by URL or ID and get back its title, creator, duration, cover art, and streaming links, plus every video currently using that sound with captions, hashtags, and engagement counts.
1. Choose the data you need
Review the published README for supported collection modes, examples, and limits. The recipe below uses the current published input definition.
2. Prepare a source-based input
This JSON contains published prefills and required-field defaults. Review every value for your task before running it; it is not a promise of successful collection.
{
"includeErrorRows": false,
"includeMusicMetadata": true,
"includePosts": true,
"maxPostsPerSound": 5,
"mode": "bySound",
"musicIds": [
"7595604258835401494"
],
"publishedWithin": "all",
"uniqueCreatorsOnly": false
}
Download input.example.json and save your reviewed copy as input.json.
| Field | Type | Required | Description |
|---|---|---|---|
mode | string | optional | Choose how to find sounds: by sound URL/ID, or by keyword search. |
musicUrls | array | optional | (mode=bySound) TikTok sound page URLs. Example: https://www.tiktok.com/music/original-sound-7595604258835401494 |
musicIds | array | optional | (mode=bySound) Numeric TikTok sound IDs, 15-20 digits, as an alternative to full URLs. |
searchQueries | array | optional | (mode=searchSounds) Keywords to search in TikTok's sound catalogue, e.g. lofi, phonk, afrobeats. Each query returns up to 30 sounds; duplicates are removed across queries. |
maxSoundsPerQuery | integer | optional | (mode=searchSounds) Keep at most this many sounds per keyword. TikTok returns a maximum of 30. |
maxPostsPerSound | integer | optional | Videos to collect per sound (0-500). Set 0 for sound metadata only. TikTok can cap the public feed per run, so fewer rows may be returned and the run status reports any shortfall. |
includeMusicMetadata | boolean | optional | Emit a metadata row per sound with title, creator/artist, duration, covers, DSP IDs, tags and video count. |
includePosts | boolean | optional | Emit one row per video that uses the sound, with author, caption, hashtags, mentions, POI, effects, slideshow images and engagement counts. |
includeErrorRows | boolean | optional | Emit a row with rowType='error' when an input cannot be read, instead of only logging it. Off by default. |
publishedWithin | string | optional | Keep only videos published inside this window. Applied after collection, to video rows. |
minPlayCount | integer | optional | Drop videos below this play count. 0 keeps everything. Videos without a play count are kept only when this is 0. |
minLikeCount | integer | optional | Drop videos below this like count. 0 keeps everything. Videos without a like count are kept only when this is 0. |
uniqueCreatorsOnly | boolean | optional | Keep only the highest-play video per author across the run. Useful for audience and creator discovery. |
3. Start an Actor run
Set APIFY_TOKEN in your environment. Python 3.10 or newer is sufficient; this recipe uses no third-party packages.
Execution may incur charges. Review current pricing on Apify. The request asks for a 120-second timeout and a charge limit; these settings are subject to Apify’s pricing and do not guarantee an all-inclusive spending cap.
import json
import os
import urllib.request
# Save the schema-derived example as input.json; review and edit it first.
with open("input.json", encoding="utf-8") as stream:
actor_input = json.load(stream)
token = os.environ["APIFY_TOKEN"]
request = urllib.request.Request(
"https://api.apify.com/v2/acts/IqJBdUeSYHgtHc7Lb/runs?timeout=120&maxTotalChargeUsd=0.50",
data=json.dumps(actor_input).encode("utf-8"),
headers={"Authorization": "Bearer " + token, "Content-Type": "application/json"},
method="POST",
)
# This starts a potentially billable run. Do not automatically retry this POST.
with urllib.request.urlopen(request, timeout=40) as response:
run = json.load(response)["data"]
print("Run ID:", run["id"])
print("Status:", run["status"])
# Inspect and download results in Apify Console once the run succeeds.
4. Inspect the actual results
Open the run in Apify Console and wait for a successful completion. Use the published output schema to locate results and the dataset schema to understand declared views. Missing or optional record fields must not be treated as guaranteed values.
Sound metadata rows (rowType=music), videos using each sound (rowType=post), and optional error rows (rowType=error), joined by matchedMusicId and searchKeyword.
Questions before you run
Which inputs are required?
No top-level fields are marked required in the published schema. Conditional requirements can still apply; check the README.
What does this guide verify?
The fields, prefills, and schema links are rendered from the published build. This is a usage recipe, not a paid live extraction test. Source availability and collection results can vary.
What if the run request times out?
Check Apify Console before retrying. The first request may already have created a run. Do not automatically repeat a run-creation POST.
Generated from source build LmWHGTW7L3zReLZ3O and its README and schemas. Source changes regenerate this guide; no third-party editorial claims are inferred.