Look Up a TikTok Profile by User ID
View all TikTok Profiles, Videos & Sounds API endpoints →Retrieve TikTok profile information for a known user ID through GET /user/id/{user_id}. The required user_id path parameter is a string representing the numeric TikTok user identifier, not a username or profile URL. Its documented default and example are 127905465618821121. Preserve the full identifier as text rather than converting it to a floating-point number. This operation has no documented pagination or feed inputs. No response example or observed response is available for this ID-based lookup. No profile field names, nested objects, counters or missing-user response shape are verified. Do not assume this endpoint returns the same fields as a username-based lookup. Validate the actual response before mapping profile attributes into a creator database; only use attributes that the response supplies.
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-data-by-id API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tiktok/user-data-by-id?key=<API_KEY>&user_id=127905465618821121'
Query Result
Use Cases
- Refresh available profile metadata in a creator database already keyed by user_id without asking analysts to re-enter account handles.
- Enrich known video-author user IDs with profile information after confirming the fields returned by the ID lookup.
- Reconcile creator records from multiple imports using their stored numeric user IDs rather than matching on display names.
- Build a profile review tool that accepts long user IDs as text and maps only response attributes verified during integration.
Frequently asked questions
What value belongs in user_id?
Supply the numeric TikTok user identifier as a string. The documented example and default are 127905465618821121. A username or profile URL is not the documented input for this endpoint.
Why should I keep the user ID as a string?
The parameter is defined as a string, and the documented example is a long numeric identifier. Converting it to a floating-point number can change its digits. Preserve the identifier exactly as received.
Which profile fields does the ID lookup return?
The operation is documented to retrieve user profile information, but no response example or observed response is available. Exact field names, nesting and counters remain unverified; do not copy a username-lookup schema without checking this endpoint.
Can I use this to refresh a record when I only stored the user ID?
Yes, a known user ID is the documented lookup input, so a stored username is not required. Validate the response before updating your record; the behavior for unavailable or missing accounts is not documented.
Does this lookup also return the user media feed?
This operation is documented as a profile-information lookup, not a posts feed, and accepts no pagination parameters. Use the separate user-media-feed-by-id operation for the documented ID-based media-feed capability.