TikTok reference
TikTok API guide
Look up public creators, collect their videos and read the discussion around a video. Use keyword, hashtag and sound discovery when you do not already know the account.
Quickstart
Start with TikTok
Look up public creators, collect their videos and read the discussion around a video. Use keyword, hashtag and sound discovery when you do not already know the account.
These requests use your API key and can spend credits. Check the current price on the endpoint page; each new page is a separate request. Later examples use illustrative identifiers: replace them with values from your earlier response.
1. Start with a creator
Read the public identity and counts. Keep numeric account IDs as strings. Parameters and current cost →
curl "https://www.monocrawl.com/v1/tiktok/profile?handle=nasa" \ -H "x-api-key: mn_your_key_here"
2. Read their videos
Keep the same handle and filters while following the returned cursor. Choose a returned video URL for the next step. Parameters and current cost →
curl "https://www.monocrawl.com/v1/tiktok/profile-videos?handle=nasa" \ -H "x-api-key: mn_your_key_here"
3. Read a video’s comments
Replace the example URL with a video URL from the previous response. A comment page and a reply thread are separate reads. Parameters and current cost →
curl "https://www.monocrawl.com/v1/tiktok/post-comments?url=https%3A%2F%2Fwww.tiktok.com%2F%40nasa%2Fvideo%2F7665075736742530317" \ -H "x-api-key: mn_your_key_here"
Filters and coverage
Choose filters with the source behavior in mind
| Control | Behavior and limits |
|---|---|
| Identity | Use a handle, with or without @. user_id is an exact numeric string, not sec_uid; retain the handle when using profile/full. Never convert a TikTok ID to a JavaScript Number. Endpoint reference → |
| Ordering and region | sort_by accepts latest or popular. region defaults to GB and controls the source request location; it is not a filter for the creator’s residence. Keep both unchanged when paging. Endpoint reference → |
| Search filters | sort_by accepts relevance (default) or most-liked, unlike the account feed’s latest/popular values. date_posted restricts the source query by publication date, for example past-week. A source that cannot honor a combination may reject it rather than silently return an unfiltered result. Endpoint reference → |
| Continuation | Pass the returned cursor unchanged. max_cursor is a compatibility alias; cursor wins when both are supplied. A source page can contain fewer results than requested. No cursor is not a guarantee of complete account history. Endpoint reference → |
| Content depth | A caption is not a transcript. Request the transcript endpoint for spoken words. trim selects the trimmed response representation; it is not a caption-length limit. Endpoint reference → |
Source availability, ordering and field coverage can change. Inspect warnings and partial-result metadata alongside the rows. See runnable workflows, metric semantics, computed fields and the pagination matrix.
Choose an endpoint
Match the operation to your task
| Your task | Endpoint | When to use it |
|---|---|---|
| A known creator | profile | Account information without retrieving a video page. |
| A creator and a bounded content sample | profile/full | One bundle with component results and computed sample statistics. |
| Videos matching a phrase | search | Keyword discovery; its results are not the account’s full publishing history. |
| One video’s caption and counts | post | Use a transcript endpoint when you need spoken words instead of the caption. |
Explore all documented operations by purpose below. Each endpoint reference contains its accepted parameters and current price.
Other operations
Posts and media
Comments and replies
Search and discovery
Transcripts
Accounts and audiences
Operations
TikTok
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
TikTok
36 operationsElsewhere
The same registry, other shapes
- TikTok overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=tiktok— the same rows to your code at runtime, for 0 credits.