---
title: "Get one item's payload"
method: GET
path: "/v1/batch/{batchID}/tasks/{seq}/content"
tags: ["Batch"]
---

# Get one item's payload

`GET /v1/batch/{batchID}/tasks/{seq}/content`

## Request

- Base URL: `https://api.spicrawl.com`
- URL: `https://api.spicrawl.com/v1/batch/{batchID}/tasks/{seq}/content`
- Auth: HTTP bearer

Returns a single finished item's payload verbatim (not wrapped), capped at 512 KiB. Use it to fetch one URL's
output without paging the whole result set.
Status meanings: 200 payload; 409 either "not finished yet, poll the job and ask again" or "finished as
failed/cancelled/skipped, will never have content" (read `detail`; for failures, `POST .../retry`);
404 `seq` is beyond the job's item count; 503 the deployment has no per-item payload to serve.
Note: the worker currently writes one stitched file per job and no per-item reference, so this endpoint
answers 503 for succeeded items in practice — read `result.content` from the results endpoint instead.
Retention is not checked here.

## Response `200`

The item's payload.

- unknown

## Other responses

- `400`: The request is invalid. Not retryable; fix the request using `code` and `diagnostics.hint`.
- `401`: Missing, invalid, revoked or expired key. Not retryable with the same key.
- `403`: The key lacks the scope this route requires (`ERR::AUTH::INSUFFICIENT_SCOPE`), or the action is not permitted.
- `404`: No such resource for this key's organization.
- `409`: Conflicts with the resource's current state, for example a session in use (`ERR::SESSION::BUSY`, retryable).
- `500`: Internal error. Retryable when `retryable` is true.
- `503`: No proxy exit or engine capacity was available. Retryable after `Retry-After`; 0 credits.

---

[API](https://skmtc.dev/spicrawl/apis/spicrawl-api.md) · [All operations](https://skmtc.dev/spicrawl/apis/spicrawl-api/llms.txt) · [OpenAPI document](https://skmtc.dev/spicrawl/apis/spicrawl-api/revisions/c4b4c6f97219?raw)