Get TikTok profile by secondary user ID
View all TikTok Profiles, Videos & Sounds API endpoints →Retrieve TikTok user profile information using the required sec_user_id path parameter. Supply an existing secondary user identifier exactly as stored, rather than an @username or the numeric user_id used by other routes. This lookup supports resolving secondary-ID references in imported records and refreshing profiles when a current username is unavailable. The documentation describes a user-profile response but does not name any response fields. No probe result or source response example is available for this operation, so the response envelope, profile-field names and any returned identifiers remain unverified. Inspect an actual response before defining field mappings; profile statistics, images and private-account data are not established by the supplied evidence.
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-sec-id API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tiktok/user-data-by-sec-id?key=<API_KEY>&sec_user_id=MS4wLjABAAAAwAg0rSzO65WQfz4RzQgGv2Xdv108BgPXhRrrmNVIHQZ9PO8-flwwRtEppYTS0OjA'
Query Result
Use Cases
- Enrich imported TikTok video records that already contain sec_user_id with available profile information while retaining the original reference.
- Refresh a secondary-ID-keyed creator catalog when the current TikTok username is absent from the source dataset.
- Build a secondary-ID-to-profile mapping for dataset joins, recording only identifier fields actually returned.
- Queue unresolved secondary-ID references for manual review instead of treating an unavailable profile as proof that an account was deleted.
Frequently asked questions
What value belongs in sec_user_id?
Use an existing TikTok secondary user identifier, sometimes called secUid. Preserve the opaque string exactly; an @username or numeric user_id is not a substitute for this path value.
Do I also need the numeric TikTok user ID?
No. This route has only one documented input: the required sec_user_id path parameter. It does not require a user_id value.
Can this endpoint find a secondary ID from a username?
No username input is documented here. This operation starts with a known sec_user_id and requests profile information; it is not documented as a username-to-secondary-ID conversion route.
Which profile response fields can I rely on?
The supplied documentation describes profile information without naming response fields, and this operation has neither an observed probe response nor a source response example. Confirm the actual envelope, field names and optional values before relying on them.
How should I associate the result with an imported secondary-ID reference?
Keep the submitted sec_user_id alongside your saved response and collection time. Compare only identifiers actually present in the returned data; do not assume the response echoes sec_user_id or supplies a numeric user_id.