Go to App

Sandbox Mode

Sandbox mode lets you build and test an integration before running a real export. A sandbox job finishes instantly, returns fixed sample data shaped like a real export from the same platform, and is never counted against your limits.

Enabling Sandbox Mode

Send the X-Sandbox: true header (or the ?sandbox=1 query parameter) when you create a job:

bash
curl -X POST https://exportcomments.com/api/v3/job \
-H "X-AUTH-TOKEN: your-api-key" \
-H "X-Sandbox: true" \
-H "Content-Type: application/json" \
-d '{
"url": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
"options": { "limit": 2 }
}'

The job comes back already done, with the sample rows inline in data:

Response โ€” Sandbox Job201
json
{
"guid": "1669aa49-50fd-4139-8fb1-3bce342d1f1c",
"status": "done",
"sandbox": true,
"replies": false,
"shares": false,
"likes": false,
"locked": false,
"timezone": "UTC",
"batch_id": null,
"options": [],
"raw_file": "75170fc230cd88f32e475ff4087f81d9-19a6b383-d1bb-4396-9e6f-24ebf22dafdf.json",
"json_url": "https://exportcomments.com/exports/75170fc230cd88f32e475ff4087f81d9-19a6b383-d1bb-4396-9e6f-24ebf22dafdf.json",
"download_link": "https://exportcomments.com/exports/yt-comments_dQw4w9WgXcQ_7b4928577e6e.xlsx",
"result_note": null,
"data": [
{
"video_id": "1gCkju1ydqu",
"channel_id": "UCeJmUNoc4y3CDhgydks5Gj9",
"author_name": "Mr. Jeremie Powlowski Jr.",
"comment_body": "Who else is watching this in 2026? ๐Ÿ‘‡",
"time": "1758050134",
"like_count": 707,
"reply_count": 40,
"comment_id": "338187283463776",
"_sandbox": true
}
]
}

The example above is shortened: each row carries every field listed under Sample data by platform.

How to recognise a sandbox response

SignalWhere
X-Sandbox: true response headerOn the create response. Present only when sandbox data was actually served
"sandbox": trueOn the job object (create, retrieve, list) and in webhook payloads
"_sandbox": trueOn every sample row

Check the response header rather than assuming: an endpoint that does not support sandbox mode ignores the request header, runs normally, and does not send the response header back.

What sandbox mode covers

Sandbox mode applies to job creation. The job it creates is stored like any other, so the endpoints that read a job work on it unchanged.

RequestIn sandbox
POST /api/v3/job with X-Sandbox: trueReturns a finished job with sample rows. No export runs
GET /api/v3/job/{guid}Returns the sandbox job (status: "done", sandbox: true)
GET /api/v3/jobsIncludes sandbox jobs, marked sandbox: true
GET /api/v3/job/{guid}/dataReturns the same sample rows as JSON or CSV (?format=csv)
Webhooksexport.finished is delivered to your endpoints, signed as usual, with sandbox: true
Everything else (webhooks, schedules, workflows, proxies, batch export)Not sandboxed. The header is ignored and the request acts on your real account
โš ๏ธ
Only job creation is sandboxed

Sending X-Sandbox: true to an endpoint that creates a schedule, workflow, webhook or batch still creates the real thing. Sandbox the job, not the automation around it.

Sample data by platform

The platform is detected from the URL, exactly as for a real export, and decides which fields each row has. Pick a platform to see the first row a sandbox job returns for it:

youtube.com ยท 25 fields
json
{
"video_id": "1gCkju1ydqu",
"channel_id": "UCeJmUNoc4y3CDhgydks5Gj9",
"community_id": null,
"author_name": "Mr. Jeremie Powlowski Jr.",
"author_thumbnail": "https://i.pravatar.cc/150?u=ebbdc49f-4dda-330f-8088-6448dcb9da98",
"profile_id": "3222211843",
"comment_body": "Who else is watching this in 2026? ๐Ÿ‘‡",
"time": "1758050134",
"message_type": "text",
"is_moderator": false,
"is_verified": true,
"is_artist": false,
"is_member": false,
"is_liked": true,
"is_hearted": false,
"is_pinned": false,
"like_count": 707,
"dislike_count": 77,
"comment_id": "338187283463776",
"author_is_channel_owner": false,
"is_community": false,
"reply_count": 40,
"reply_token": null,
"replies": [],
"sentiment": null,
"_sandbox": true
}
Field list (25)
FieldType
video_idstring
channel_idstring
community_idnullable
author_namestring
author_thumbnailstring
profile_idstring
comment_bodystring
timestring
message_typestring
is_moderatorboolean
is_verifiedboolean
is_artistboolean
is_memberboolean
is_likedboolean
is_heartedboolean
is_pinnedboolean
like_countinteger
dislike_countinteger
comment_idstring
author_is_channel_ownerboolean
is_communityboolean
reply_countinteger
reply_tokennullable
repliesarray
sentimentinteger

These samples are generated by the API itself, so they match what you receive field for field.

The data is fixed

  • The same platform always returns the same rows, in the same order. You can assert on exact values in your tests.
  • options.limit returns the first N rows of that fixed list (default 10, maximum 100). Values below 1 are raised to 1.
  • Timestamps are fixed too. They fall in the 180 days before 15 January 2026 and do not move with the current date.
  • Names, text, ids and image URLs are invented. Ids are not real and cannot be looked up on the platform.
  • A URL from a platform the sandbox cannot identify gets the YouTube sample.

What you can test

  • Request validation. Sandbox requests are validated like real ones. A missing or malformed url returns the same 400 and the same error body, without the X-Sandbox response header.
  • Your parsing code. Rows have the field names and JSON types of a real export for that platform.
  • Polling. GET /api/v3/job/{guid} returns the job. It is already done, so sandbox mode cannot show you the queueing and progress states.
  • Webhook handling. Your endpoint receives a signed export.finished delivery for each sandbox job.
  • Reading results. GET /api/v3/job/{guid}/data and the json_url file return the sample rows.

Differences from a real export

SandboxReal export
Quota and rate limitsNot counted, not limitedCounted against your tier
SpeedFinished in the create responseAsynchronous, poll or use webhooks
Create responseIncludes data and sandbox: trueReturns the job without rows
RowsFixed sample, 100 at mostLive data, up to your plan limit
Row shapeThe platform's standard comment or review fieldsDepends on what you export (comments, followers, likes, posts, reviews)
options other than limitAccepted but ignoredApplied
Excel/CSV file at download_linkNot generated. Use /data or json_urlGenerated
RetentionDeleted after 24 hoursKept according to your plan
Retry and stopNot applicable, the job is already doneAvailable
๐Ÿ’ก
Rows from the data endpoint have extra fields

GET /api/v3/job/{guid}/data returns the same rows with additional normalised fields (for example url, giveaway_* and analytics_*). That is true for real exports as well, so code written against the sandbox works unchanged.