Search users

search · $0.0040

The Users tab — and the only way to turn a name into a profile id.

POST https://api.sorina.sh/v1/tiktok/search/users

Body

fieldtypewhat it is

keyword string

A handle, a name, a phrase.

cursor integer?

Where to start. This tab pages on cursor, not offset, and sending offset is a 400 naming the field.

count integer?

Page size. Defaults to 10.

search_id string?

Required from the second page on: the first page’s x-tt-logid.

A type written with ? is optional. Unknown fields are rejected rather than ignored, and the whole body is capped at 64 KiB.

Example

curl -X POST https://api.sorina.sh/v1/tiktok/search/users \
  -H "authorization: Bearer $SORINA_KEY" \
  -H 'content-type: application/json' \
  -d '{"keyword":"nasa","cursor":0,"count":10}'

What comes back

JSON, around 88 KB — the smallest of the verticals. Results are under user_list, each {user_info, challenges, effects, items, mix_list, musics}.

user_list[].user_info is a full profile object of roughly a hundred keys, including sec_uid — the id /users demands and nothing else on this API produces. Searching a handle here and passing the sec_uid to /users is the whole “name to profile” path.

bold_fields marks which fields matched the query, which is a cheap way to tell a handle match from a display-name one. cursor and has_more page it; input_keyword echoes what you asked.

pages on cursor

Send the value the previous response returned, not one you counted. Page two and later must also carry the first page's x-tt-logid back as search_id, or the call is refused with 400 search_id_required. Pagination has the rest.

/search/videos

/search/music