GET /v1/render-outputs/{id}
Download a previously rendered document. The URL is provided in the response from POST /v1/render when using URL delivery.
Endpoint:
GET /v1/render-outputs/{id}Path Parameter
Section titled “Path Parameter”| Parameter | Type | Description |
|---|---|---|
id |
string |
The render job ID (UUID) from the render response, or a batch ID. |
Batch IDs
Section titled “Batch IDs”A batch’s url uses its batchId and downloads the whole batch as one file:
- PDF: the document, one label per page.
- ZPL: every label block joined in input order, ready to send to a printer.
PNG and HTML batches have no combined file: download each label from its own items[].url, which is a render job ID like any other.
Authentication
Section titled “Authentication”Requires the same API key (or session token) used to create the render.
Authorization: Bearer bp_sk_live_YOUR_KEYResponse
Section titled “Response”Status: 200 OK
The response body contains the rendered document. The Content-Type header matches the format:
| Format | Content-Type |
|---|---|
application/pdf |
|
| PNG | image/png |
| ZPL | text/plain |
| HTML | text/html |
Cache: private, max-age=3600
Example
Section titled “Example”curl -H "Authorization: Bearer bp_sk_live_YOUR_KEY" \ "https://api.binderypress.dev/v1/render-outputs/a1b2c3d4-e5f6-7890-abcd-ef1234567890" \ -o output.pdfErrors
Section titled “Errors”| Status | Code | Cause |
|---|---|---|
401 |
AUTH_REQUIRED |
Missing or invalid API key. |
404 |
NOT_FOUND |
Job or batch ID not found, output has expired (older than 7 days), or a PNG or HTML batch ID (no combined file). |