Get a TikTok Creator's Media Feed by Username
View all TikTok Profiles, Videos & Sounds API endpoints →Retrieve a TikTok creator's media feed using the required username path parameter as a string, such as khaby.lame. The optional max_cursor and min_cursor query parameters are strings; omit both for an initial request. A successful observed request returned HTTP 200 with status=ok and ten videos in data.aweme_list, together with has_more=1 and min_cursor/max_cursor pagination fields. Video records in that sample included video identifiers, author information, creation timestamps, engagement statistics and playable media URLs. The first observed aweme_id was 7697307919943060767, belonging to khaby.lame, with a creation date of 2026-10-16 and 3363153 reported views at collection time. These are sample observations, not fixed response values or a guarantee that every page contains ten items. Supplied research also identifies descriptions as useful feed content, but their exact response field name is not established in this evidence. No separate response example was available to confirm additional nested field names. Use the returned cursor fields as candidate continuation checkpoints, retaining their values as strings; the correct cursor combination, direction and multi-page behavior were not verified. Deduplicate collected items by video ID and stop on repeated checkpoints. The endpoint exposes no count parameter. Do not infer chronological order, complete posting history, private creator analytics or permanent media access from the observed page.
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/user-media-feed-by-username API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tiktok/user-media-feed-by-username?key=<API_KEY>&username=khaby.lame'
Query Result
Use Cases
- Build a recent-content review queue for a known creator using feed video identifiers and available media links, adding descriptions when present.
- Select individual feed videos for enrichment through the separate video-data lookup, joining records by aweme_id instead of matching captions.
- Store collection-time engagement snapshots beside feed video IDs for editorial comparison without presenting them as creator-private analytics.
- Prototype a bounded multi-page creator-content collector that validates returned cursors, removes duplicate video IDs and halts when a checkpoint repeats.
Frequently asked questions
Do I need the creator's numeric user ID to request this feed?
No. This route requires a username string, such as khaby.lame. It is a handle-based media lookup, unlike the separate user-ID routes.
What did the successful media-feed request return?
The supplied HTTP 200 observation reported status=ok, ten records in data.aweme_list, has_more=1 and min_cursor/max_cursor fields. The records contained video identifiers, author information, creation timestamps, engagement statistics and playable URLs. Exact nested field names beyond the reported aweme_id were not established here.
How should I use max_cursor and min_cursor?
Both are optional string query parameters. Omit them for the first request, then retain returned cursor values as candidate checkpoints. Cursor direction, whether one or both should be sent, and successful continuation were not verified. Validate those details in a bounded test and stop on repeated checkpoints or duplicate-only results.
Can I set a page size or assume newest-first order?
No count parameter is documented for this operation. Ten videos were observed on one page, but that does not establish a fixed page size, chronological ordering or complete posting-history coverage.
Are feed statistics and playable URLs suitable for permanent records?
Store video IDs and collection timestamps as the basis for your records. Engagement counters reflect a collected snapshot, not historical or private analytics. Playable URLs were observed but should not be treated as permanent media assets; handle unavailable links separately.