TikTok Hashtag Posts API
Use the TikTok Hashtag Posts API with a full tag URL or name. Read public video records, authors and engagement, then continue only when a usable new cursor is returned.
1 credits per non-empty successful request; empty results and failures are free. Each page is billed separately.
Each page requests 20 records; the returned number can vary. Next page is a separate billed request.
https://api.goanyapi.com/api/v1/tiktok/hashtag-posts?url=https%3A%2F%2Fwww.tiktok.com%2Ftag%2Ffyp&cursor=0&count=20Run a request to see the visual result
The response is organized into metrics, lists and tables that match the JSON on the right.
Run a request to see the response here
Fill in the demo parameters to preview an example response for free. Sign in to send live requests with your own parameters.
Read the posts returned for one hashtag
The TikTok Hashtag Posts API retrieves a page of available public posts for a known tag. Start with its full URL or name; no separate tag-details lookup is required. Each record can contain a video description, author, creation time, engagement and media information. This gives a content index or review tool individual records to display rather than a single hashtag count. The API documentation provides the full input and output reference.
A tag request becomes a list of post records
For a request example, send GET /api/v1/tiktok/hashtag-posts?challenge_name=fyp&cursor=0&count=20 with your GoAnyAPI Bearer API key. You can replace the name with url=https://www.tiktok.com/tag/fyp; do not send both. This demonstrates the request syntax, not a fresh response. Read data.items[] as the current page, and inspect each item’s id, desc, author, stats and video objects. The number of array entries is the actual page length. A tag’s overall video count belongs to its profile, whereas this array contains the posts returned by this particular query. Use an individual video URL or ID with the Video Details API when you need to inspect that post separately.
- data.items[].id / data.items[].desc
- The post ID identifies the individual record; desc contains its returned description. Keep IDs as returned when storing or linking records. A description is post text, not the hashtag’s profile description, a transcript, or an automatically generated assessment of the video.
- data.items[].author
- The author object can include id, uniqueId, nickname, avatars and a verification flag. The handle and display name serve different purposes: a nickname is presentation text and should not be treated as a unique account identifier. Missing author fields need their own empty state.
- data.items[].createTime
- This is the returned creation-time field for the post. It is separate from the time your application retrieves or saves the response. If you show a formatted date, keep the source value and make your display timezone clear rather than treating retrieval time as publication time.
- data.items[].stats / data.items[].statsV2
- Read playCount, diggCount, commentCount, shareCount and collectCount where present. They represent available public counts, not unique viewers or conversion data. Keep the two statistics objects distinct. A comment count is not comment text, and an unavailable count should not be displayed as a measured zero.
- data.items[].video
- Media fields may include cover, originCover, dynamicCover, playAddr, downloadAddr, dimensions and duration. Use a cover for a visual preview when available. Returned addresses do not promise permanent access or a watermark-free file. The diagram illustrates these field relationships; it does not add media data to a response.
- data.hasMore / data.nextCursor / data.pageSize
- These describe page continuation and the configured request size, not a result total or a guaranteed next page. A cursor can be present while hasMore is false; that does not justify continuing. Read both signals together and keep your saved request associated with its response.

Continue only when both pagination signals allow it
The request count is fixed at 20. data.pageSize records that request size; actual entries are counted from data.items.length and can be fewer. Continue only if data.hasMore=true and data.nextCursor is valid and different from the cursor just used. Keep the tag URL or name unchanged and pass that returned value as cursor. Stop if either condition is missing. Do not generate an offset by adding 20, infer a total from the page size, or promise a complete history from the pages you obtain.
Keep content, identity and page metadata distinct
Show a post list
Use each returned record to display the description, available author information and a cover preview. Preserve incomplete records without inventing missing fields.
Inspect public engagement
Read the counts attached to each post. Any sorting, grouping, deduplication or comparison in your application is your own processing of the returned records.
Check request costs
Each nonempty successful page is billed independently at the current configured rate. URL and identifier handling add no separate charge; empty results and failures are free.
Frequently asked questions
Yes. Use a full HTTPS /tag/ URL on tiktok.com or www.tiktok.com, or challenge_name without # or spaces. Choose one input. Short links on vm.tiktok.com or vt.tiktok.com are unsupported. No separate ID lookup is required.
No. The request asks for a fixed count of 20, and pageSize reports that setting. Use the actual items array to determine how many entries came back. It is not a total count, and this page makes no guaranteed output-length claim.
It retrieves posts for the tag you specify. It is not a free-text caption or comment search, and the returned order is not a guaranteed popularity or chronological ranking. Private, deleted or unavailable content and complete historical coverage are not promised.
No. This is a synchronous GET query. Viewing the saved example does not make a new request. Each real next-page query is a separate request, and the response reports its creditsUsed and remainingCredits.
Continue with a video or author
Video Details retrieves one post, User Profile returns public account information, and User Posts lists available posts by profile URL or username.