TikTok User Posts API
Use the GoAnyAPI TikTok User Posts API to query public videos by profile URL or username. Each request asks for 15 records; read the returned items and continue with a valid new cursor.
1 credits per non-empty successful request; empty results and failures are free. Each page is billed separately.
Each page requests 15 records; the returned number can vary. Next page is a separate billed request.
https://api.goanyapi.com/api/v1/tiktok/user-posts?url=https%3A%2F%2Fwww.tiktok.com%2F%40spidey.glow&cursor=0&count=15Run 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.
From an account to a page of public videos
The TikTok User Posts API retrieves available public posts for a known account. Use it when a profile’s follower or video count is not enough and you need the individual video records: descriptions, authors, publication times, public engagement and media fields. A developer can turn these records into a content list; an editor can inspect what the returned posts actually contain. The response separates data.items[] from pagination information, so you can read each video without mistaking the page size for an account total. See the API documentation for the input choice and complete fields.
Input → item array → returned cursor
Supply https://www.tiktok.com/@spidey.glow or the username spidey.glow, without @. You do not need to query User Profile or obtain a secUid first. The initial cursor is the string 0, and the request count is fixed at 15. In the response, each entry in data.items[] is a video record; inspect its id, desc, createTime, author, stats, statsV2 and video fields where present. Then inspect data.hasMore and data.nextCursor before deciding whether to request another page. This is an input-and-field example, not a new query or a claim about the account’s current post count. The diagram illustrates these relationships; the Tester’s JSON contains the actual saved example or your returned result.
- Video rows · data.items[]
- Read the array as the records returned on this page. Each item’s ID identifies a post, while IDs inside
authoridentify the account. Preserve those roles when saving rows. A page can contain fewer records than requested; do not fill missing rows with invented videos. - Content and time · data.items[].desc, data.items[].createTime
- Use the description to display the post text and the Unix timestamp in seconds to display its publication time. Description text is not an audio transcript. Publication time belongs to the video; it is distinct from your own retrieval or observation time.
- Author · data.items[].author
- The returned username, nickname and available avatar fields can identify the author beside each item. They are not an audience profile. If you need account-level biography or public statistics, a separate User Profile request can supply its own result.
- Engagement · data.items[].stats and data.items[].statsV2
- Available play, like, comment, share and save counts belong to the individual post. Read the returned values without adding parallel fields together. Missing and empty counts are not zero, and public engagement alone does not establish sales, unique viewers or viewing completion.
- Media · data.items[].video
- Available cover variants, duration, dimensions and media addresses support a video list or detail view. Handle missing values and inaccessible images in your own interface. The endpoint does not guarantee a permanent download address or a watermark-free file.
- Request size · data.pageSize
- This describes the fixed request size of 15, not the actual number of returned rows. Count
data.items.lengthfor the current page. Neither value is an account-wide total, and a short page alone does not justify inventing a cursor or declaring a complete history. - Continuation · data.hasMore, data.nextCursor
- These fields describe whether another page is reported and which continuation value was supplied. A true flag without a usable new cursor is insufficient to continue. Keep the account input and returned cursor together so that the next request addresses the same list.

Continue only with the returned pagination information
Use either url or username, never both, and use a full HTTPS profile URL rather than a short link. Keep that same account input when paging. Continue only when data.hasMore is true and data.nextCursor is valid and different from the current cursor; pass that value unchanged as cursor. Stop on a missing or repeated cursor, even if more results are reported. Do not calculate an offset or substitute a date. Each nonempty successful page is independently charged at this API’s current configured rate. URL and account resolution add no separate charge; empty results and failures are free.
Work with the returned posts
Display a content list
Developers can show descriptions, available covers and public counts from the returned items. The API supplies records; your application handles display, storage and any deduplication across separately retrieved pages.
Review individual videos
Editors can inspect each returned post and open a separate Video Details lookup for a selected ID or full video URL. Comments require their own interface; a comment count does not contain the discussion.
Compare your collected records
Sorting, grouping descriptions and comparing saved observations are operations you implement after retrieval. The endpoint does not provide automatic topic labels, a popularity ranking, scheduled monitoring or a guarantee that page order remains unchanged.
Frequently asked questions
No. The request size is fixed at 15, rather than a user-selectable count. Read the actual item array for what was returned. A fixed request size is not a guarantee that every page contains 15 items.
There is no complete-history or stable-order guarantee. Private, deleted or unavailable posts may not be returned. Record the scope you actually retrieved, and use only valid new response cursors to continue.
An empty result or failed request is free. A new nonempty successful request is independently billable, including another page or a repeated query. Check the current rate in the Tester and the returned creditsUsed and remainingCredits for settlement.
No. Query posts directly with a supported full profile URL or username. URL resolution has no separate charge. Only an optional, separately requested User Profile lookup is settled under that API’s own billing rules.
Read a video, profile or tag in detail
Use Video Details to inspect a selected post, User Profile for public account information, and Hashtag Details for a known tag’s description and available counts.