TikTok API

TikTok Comment replies API

List the replies to a TikTok comment with cursor pagination (text, author, likes).

$0.60/1k req, pay per request, no subscription.

What the API returnedcomments[0]
{
"id": "7623828998112345601",
"text": "This is actually so real, been saying this for years",
"author": "marcusreidfit",
"likes": 842,
"createdUtc": 1758153600,
"videoId": "7623818255903329566",
"authorName": "Marcus Reid",
"authorImage": "https://p16-sign-va.tiktokcdn.com/tos-maliva-avt-0068/marcusreidfit~c5_100x100.jpeg?x-expires=1759104000&x-signature=abc123",
... 1 more field
}
Uptime
100.00%
30d · 8,169 calls
Requests
8,196
30d · weekly, last 12 wks
Response
0.4s
median · 30d

Pricing and providers

TikTok Comment replies API pricing: one API, 4 interchangeable providers

The cheapest provider serves first. If it fails, the next one takes over in the same call.

You pay
$6.00
$0.60/1k req, only for what you use. No monthly plan.
Your first 166 requests are free with the $0.10 starting balance.

Try it

Get TikTok comment replies in one request

requireFieldsarray
Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `authorUserId`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a reply that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.
Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.

This sample shows 12 of 14 fields. See every field

{
  "found": true,
  "data": {
    "nextCursor": "eyJvZmZzZXQiOjEwfQ==",
    "comments": [
      {
        "id": "7623828998112345601",
        "text": "This is actually so real, been saying this for years",
        "author": "marcusreidfit",
        "likes": 842,
        "createdUtc": 1758153600,
        "videoId": "7623818255903329566",
        "authorName": "Marcus Reid",
        "authorImage": "https://p16-sign-va.tiktokcdn.com/tos-maliva-avt-0068/marcusreidfit~c5_100x100.jpeg?x-expires=1759104000&x-signature=abc123"
      },
      {
        "id": "7623829102938475801",
        "text": "wait this changes everything lol",
        "author": "dana.codes",
        "likes": 214,
        "createdUtc": 1758157200,
        "videoId": "7623818255903329566",
        "authorName": "Dana Okafor",
        "authorImage": "https://p16-sign-va.tiktokcdn.com/tos-maliva-avt-0068/dana.codes~c5_100x100.jpeg?x-expires=1759104000&x-signature=def456"
      }
    ]
  }
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

One request, one response shape.

Every field you send and every field you get back, each with a real example.

Last verified 2026-10-31 · uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • commentIdstring

    7623828115408274207

    TikTok comment ID (the comment's cid from the comments endpoint).

  • urlstring

    https://www.tiktok.com/@stoolpresidente/video/7623818255903329566

    TikTok video URL the comment belongs to.

  • cursorstring

    Pagination cursor from a previous response.

  • requireFieldsarray

    Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `authorUserId`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a reply that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.

You send. A small JSON body. The values shown are examples to replace with your own.

Response

JSON, one example value per field.

each commentdata.comments[]
  • authorstring

    marcusreidfit

    Populated whenever the provider has data for the entity.

  • authorImagestring

    https://p16-sign-va.tiktokcdn.com/tos-maliva-avt-0068/marcusreidfit~c5_100x100.jpeg?x-expires=1759104000&x-signature=abc123

    Reply author's avatar image URL. Signed and short-lived, so the query string is load-bearing and kept intact.

  • authorNamestring

    Marcus Reid

    Reply author's display name.

  • authorUserIdstringcan require

    Reply author's numeric TikTok user id. Null when the serving source does not report it.

  • createdUtcnumber

    1758153600

    UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.

  • idstring

    7623828998112345601

    Populated whenever the provider has data for the entity.

  • likesinteger

    842

  • textstring

    This is actually so real, been saying this for years

    Populated whenever the provider has data for the entity.

  • videoIdstring

    7623818255903329566

    Identifier of the video the reply belongs to.

datadata
  • nextCursorstring

    eyJvZmZzZXQiOjEwfQ==

    Opaque cursor for the next page of comments, or null when this lane has no more. Pass it back as cursor to continue.

top level
  • foundboolean

    true

  • reason"not_found"

    Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.

You get back. Named, typed fields in the same shape whichever source answers.

FAQ

About the TikTok Comment replies API

The AnyAPI TikTok Comment replies API returns TikTok comment replies data as normalized JSON from one POST call to /v1/run/tiktok.comment_replies. List the replies to a TikTok comment with cursor pagination (text, author, likes). AnyAPI routes each request across 4 sources and falls back automatically when one fails. It costs from $0.60 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of TikTok comment replies calls through AnyAPI succeeded, with a median response time of 0.4 seconds across 8,169 measured calls.

It costs from $0.60 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

List the replies to a TikTok comment with cursor pagination (text, author, likes). The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of TikTok comment replies calls through AnyAPI succeeded, with a median response time of 0.4 seconds across 8,169 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.

Yes. A new AnyAPI account starts with $0.10 of free balance and no card required, which covers 166 TikTok Comment replies calls at $0.0006 each.

AnyAPI asks the next of its 4 sources in the same request, cheapest first, so one source going down does not fail your call.

Send a POST request to https://api.getanyapi.com/v1/run/tiktok.comment_replies with your AnyAPI key in an "Authorization: Bearer" header and the input as a JSON body. The same key and the same wallet work on every AnyAPI endpoint.

No. You add US dollars to one prepaid AnyAPI balance and each request draws it down. There is no monthly plan and no minimum, and the same balance pays for every AnyAPI endpoint.

Yes. Install @getanyapi/sdk from npm for TypeScript or getanyapi from pip for Python. Both call every AnyAPI endpoint with the same key, and any HTTP client works too.

Yes. An agent can connect to the AnyAPI MCP server at https://api.getanyapi.com/mcp, or create its own free-trial key with one unauthenticated POST to https://api.getanyapi.com/agent/signup and call this endpoint over HTTP.