continuationTokenstringrequired
Replies continuation token from the comments endpoint, or the continuationToken from a previous replies response for further pagination.
https://api.sandbase.ai/v1/api/youtube/comment-repliesList replies to a YouTube comment using a continuation token with cursor pagination (text, author, likes, publish time).
Your output will appear here
Complete the inputs, then click Run.
List replies to a YouTube comment using a continuation token with cursor pagination (text, author, likes, publish time).
curl -X POST "https://api.sandbase.ai/v1/api/youtube/comment-replies" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"continuationToken": "Eg0SC19fZm1EajBaSjFRGAYygwEaUBIaVWd3aXRjRk9fdmtpM0x4LUNfZDRBYUFCQWciAggAKhhVQ1g2T1EzRGtjc2JZTkU2SDh1UVF1VkEyC19fZm1EajBaSjFRQABICoIBAggBQi9jb21tZW50LXJlcGxpZXMtaXRlbS1VZ3dpdGNGT192a2kzTHgtQ19kNEFhQUJBZw=="}'
The result is returned in outputs[0].data. A lookup that finds nothing still succeeds and returns found: false.
| Name | Type | Required | Description |
|---|---|---|---|
continuationToken | string | Yes | Replies continuation token from the comments endpoint, or the continuationToken from a previous replies response for further pagination. |
Billed at the actual cost of each call, usually $0.0012 per request. A call can cost more when the first data source fails and another one answers. Failed calls are not charged. Lookups that find nothing and searches with no results are billed at their actual cost, which is often lower and can be $0.
Start building
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/youtube/comment-replies" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"continuationToken": "Eg0SC19fZm1EajBaSjFRGAYygwEaUBIaVWd3aXRjRk9fdmtpM0x4LUNfZDRBYUFCQWciAggAKhhVQ1g2T1EzRGtjc2JZTkU2SDh1UVF1VkEyC19fZm1EajBaSjFRQABICoIBAggBQi9jb21tZW50LXJlcGxpZXMtaXRlbS1VZ3dpdGNGT192a2kzTHgtQ19kNEFhQUJBZw=="
}
SANDBASE_JSON
)
printf '%s\n' "$result"Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
continuationTokenstringrequiredReplies continuation token from the comments endpoint, or the continuationToken from a previous replies response for further pagination.
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
| API | Price | Response |
|---|---|---|
YouTube Comment RepliesThis API YouTube | From $0.0012 per call | JSON |
YouTube | From $0.0004 per call | JSON |
YouTube | From $0.0012 per call | JSON |
YouTube | From $0.0012 per call | JSON |
YouTube | From $0.0012 per call | JSON |
YouTube | $0.01 per call | JSON |
Questions
Send a POST request to https://api.sandbase.ai/v1/api/youtube/comment-replies with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
From $0.0012 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
Required: continuationToken (string). The Parameters table and the Playground on this page list every field.
A JSON response returned in the same HTTP request (synchronous).
No. YouTube Comment Replies runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for YouTube API access separately.