TikTok through HasData
Four tools. hasdata_tiktok_profile_getTikTokProfile and hasdata_tiktok_posts_getTikTokPosts take a handle, hasdata_tiktok_search_getTikTokSearch takes a keyword, and hasdata_tiktok_comments_getTikTokComments takes a videoId.
type on the search chooses between video and user, so the same keyword answers two different questions depending on which one you send.
A handle that does not exist looks like a success
The call returns 200, requestMetadata.status reads ok, and the payload carries an error string with no profile or posts key. Nothing else marks it. Test for the object you came for before reading fields, or an account that does not exist is reported as an account with nothing to say.
A malformed handle is the other case and it fails the schema with a 422 on handle, so the two failures need different messages.
Engagement is on the post, not the profile
A post carries likes, comments, shares, plays, reposts and collects, alongside description, createTime, duration, width, height and an author block. The profile carries the account totals as followers, follows, friends, likes and videos.
createTime is an ISO timestamp on posts and comments, so recency is answerable directly rather than by inference.
Optional fields follow the account, not the endpoint
hashtags and mentions are present only on videos that carry them, and the rate swings with the account rather than with the tool. Sampled feeds ran from no tagged posts at all to every post tagged, so a single account tells you nothing about the next one and an absent array means this account does not tag rather than that the field is missing. Parse the description when you need tags the account wrote inline.
The media URLs are optional too. playUrl, downloadUrl, dynamicCoverUrl and ratio are missing on some videos while coverUrl is there throughout, so test the key rather than assuming a video is playable.
Paging and ids
pagination carries count, hasMore and nextPageToken on all three list tools, and the comments tool adds total, which is the whole comment count rather than the page. Read total before deciding to walk a thread, because a popular video runs to thousands and each page is a billed call.
videoId and commentId are long numeric ids that have to stay strings. Putting one through a number loses the last digits and fetches nothing. The id for a video is posts[].id from the feed or videos[].id from the search.
Replies live under replies on a comment, and replyCount says how many exist. Pulling a reply thread means passing that comment's id as commentId.
