# Download job labels (PDF)

```http
POST https://secure.yoprint.com/v1/api/store/{team_slug}/job/export_job_label
```

- API version: v1
- Operation ID: `v1_public_job_export_job_label`
- Section: Production › [Jobs](https://developer.yoprint.com/reference/jobs.md)
- Web page: https://developer.yoprint.com/reference/jobs/v1-job-export-job-label/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

Returns one PDF of 4" x 6" job labels, one per job. The PDF is made while you wait and nothing is stored.

## Permission

Any member of the team. No sales order permission is checked.

## Business rules

- Send between 1 and 100 ids. More than 100 is a 422 `limit_reached` ("we only allow export of 100 jobs at a time").
- Ids that aren't jobs of your team are skipped. When none is left the response is a 404.

## Path parameters

- `team_slug` (string, required): Your team slug, shown as Team ID next to your API key in Profile. Example `your-team`.

## Request body

Content type `application/json`, required.

The body is an array of objects.

Fields:

- `id` (string, required): The hash id of one of the jobs.

### Example request

```bash
curl -X POST 'https://secure.yoprint.com/v1/api/store/your-team/job/export_job_label' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1' \
  -H 'Content-Type: application/json' \
  -d '[
    {
      "id": "WaGvtaWsx7Kcn4"
    },
    {
      "id": "6E8Ybl4wnA5yBW"
    }
  ]' \
  -o document.pdf
```

## Response

`200` The labels as a PDF, shown inline (`Content-Disposition: inline`).

The answer is a file (`application/pdf`), not JSON. The example saves it with `curl -o`.

## Errors

- `401` The API key is missing or wrong (`unauthenticated`).
- `403` You are not allowed to do this. `api_access_not_in_plan`: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only `{"message": "Insufficient Permission"}`. Other refusals use the error envelope, with `unauthorized` or `user_is_not_authorized`.
- `404` Not found. `page_not_found`: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's. `code: null`, with a message that starts "No query results for": there is no record with that id.
- `422` The request was refused and changed nothing. `validation_failed` lists what to fix in `error.fields`; other codes name a business rule, explained in `error.message`. A few checks answer with only `{"message": "..."}`. An operation that calls another service (a payment provider, a carrier, an accounting app) can answer `connect_timeout` ("Please retry again") when that service does not answer in time: the change may or may not have happened there, so read the record back before you retry.
  - When: More than 100 ids (`limit_reached`); an item without a valid `id`; or none of the ids is a job of your team (the error code is `no_invoice_found`, even though these are jobs). Fix: Send at most 100 job hash ids of your team.

## Related

- [Download small job labels (PDF)](https://developer.yoprint.com/reference/jobs/v1-job-export-dymo-label.md): `POST /v1/api/store/{team_slug}/job/export_dymo_label`
- [Filter jobs](https://developer.yoprint.com/reference/jobs/v1-job-filter.md): `POST /v1/api/store/{team_slug}/job/filter`