This is a synthetic, offline exercise for a developer preparing a parser. Every identifier and value is invented. It uses the documented replay-response shape; it does not contact Humanbased, require an account or Key, move a reading position, or incur a charge.
1. Run the local parser
You need Python 3 and a terminal supporting a quoted heredoc (bash or zsh). Copy the complete block. It reads its fixture from memory and writes no files.
python3 - <<'PY'
import json
page = json.loads(r'''{
"data": {
"items": [
{
"submission_id": "784210006031",
"task_id": "784210005001",
"campaign_id": "784210001001",
"template_id": "784210002001",
"data": {
"case_id": "returns-014",
"decision": "escalate"
},
"quality_score": 0.85,
"quality_grade": "A",
"unit_price_usd": 0.02,
"source": "web",
"created_at": "2026-10-01T09:30:00+00:00"
}
],
"next_cursor": null,
"has_more": false,
"count": 1,
"receipt": null
},
"success": true,
"errorCode": 0,
"errorMessage": "SUCCESS"
}''')
assert page["success"] is True and page["errorCode"] == 0
items = page["data"]["items"]
assert page["data"]["count"] == len(items)
for record in items:
assert isinstance(record["submission_id"], str)
print(record["submission_id"], record["data"]["case_id"], record["data"]["decision"])
print("count:", len(items), "has_more:", page["data"]["has_more"])
PY784210006031 returns-014 escalate
count: 1 has_more: False2. Interpret the result
data.items contains delivered records. Each record's data is already a JSON object; do not decode it a second time. Preserve the identifiers as strings. This fixture has one item and no next page; live responses can be empty or paginated.
receipt: null represents a replay with no new debit for this request. It does not mean the underlying records are free. A successful local parse establishes neither live access nor usage rights.
If Python is missing, install Python 3 before continuing. An assertion or syntax error means the copied fixture or program did not match this exercise; recopy the complete block and inspect the named line. It is not a production API error.
3. Move to an authorized integration
Arrange the organizationThe Developer-side unit that holds Campaigns, data access, and funds, eligible subscription, permitted use and matching Key, then follow Get your first authorized data. Compare the actual response against Retrieve delivered records, including empty pages, cursors, errors and charges. Never substitute these synthetic IDs into a production request.