TikTok Profile API with sec_user_id and user

Retrieve TikTok user profile information by supplying both required path parameters: sec_user_id and user_id. Use a trusted pair associated with the intended account; keep the secondary identifier opaque and preserve the numeric-looking user_id as a string. This route is useful when an imported record already stores both identifiers. The documentation describes a user-profile response but provides no named response fields, and this operation has no observed probe response or source response example. The response envelope, returned identifiers and handling of mismatched pairs are therefore unverified. Compare only identifiers actually present in a response; this lookup is not evidence of account ownership, an identity-verification service or a guaranteed mismatch detector.

API Features

Paired-identifier profile request Submit sec_user_id and user_id together as two required URL path values to retrieve profile information.

Trusted-pair record refresh Reuse an identifier pair already associated with an account in an imported record, without supplying a username.

Separate ID representations Keep the opaque secondary ID and numeric-looking user ID in separate string fields rather than treating them as interchangeable.

Returned-ID comparison support Retain the submitted pair for comparison with identifiers actually present in the response, without assuming mismatches are detected.

Live API Demo

GET /api/project/tiktok/user-data-by-sec-id-and-user-id

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/tiktok/user-data-by-sec-id-and-user-id?key=<API_KEY>&sec_user_id=MS4wLjABAAAAwAg0rSzO65WQfz4RzQgGv2Xdv108BgPXhRrrmNVIHQZ9PO8-flwwRtEppYTS0OjA&user_id=127905465618821121'

curl -X GET 'https://api.opendata-api.com/api/project/tiktok/user-data-by-sec-id-and-user-id?key=<API_KEY>&sec_user_id=MS4wLjABAAAAwAg0rSzO65WQfz4RzQgGv2Xdv108BgPXhRrrmNVIHQZ9PO8-flwwRtEppYTS0OjA&user_id=127905465618821121'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Refresh a creator record from a source system that already stores a trusted sec_user_id and user_id pair.
Check identifier consistency during a database migration by comparing submitted pairs with any identifiers actually returned.
Preserve the exact two-ID lookup context alongside a profile snapshot so data-quality reviewers can trace the imported record used.
Investigate suspected cross-account joins by reviewing saved identifier pairs and returned profile data without treating the lookup as proof of identity.

Frequently asked questions

Are both sec_user_id and user_id required?

Yes. Both are required string path parameters for this operation. Supply a trusted pair associated with the intended TikTok account; neither parameter replaces the other.

Should user_id be converted to a number?

No. Although the documented example contains digits, user_id is a string parameter. Preserve its text representation and keep it separate from the opaque sec_user_id.

What happens if the two identifiers refer to different accounts?

The supplied evidence does not establish mismatch behavior. Do not assume the request will reject a conflicting pair or identify which value is wrong; inspect the actual response and compare only identifiers it returns.

Which fields does the paired-ID response include?

Only user profile information is described. No field names or response envelope are documented in the supplied material, and neither a probe result nor a source response example is available for this route.

Can a successful lookup verify account ownership?

No. Requesting profile data with a saved identifier pair does not demonstrate control of the account or verify a person. Keep the pair for record reconciliation, not as an identity-verification result.

Related operations

Guides

View Subscription Plans →

Get TikTok profile with secondary and numeric IDs