# Change a job's status (retired)

```http
PUT https://secure.yoprint.com/v1/api/store/{team_slug}/job/{hash_id}/status
```

- Status: legacy, deprecated
- API version: v1
- Operation ID: `v1_public_job_change_status`
- Section: Production › [Jobs](https://developer.yoprint.com/reference/jobs.md)
- Web page: https://developer.yoprint.com/reference/jobs/v1-job-change-status/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

> **Legacy (deprecated).** A newer operation does this better: use [Change a job's status](https://developer.yoprint.com/reference/jobs/v2-job-change-status.md) (`PUT /v2/api/store/{team_slug}/v2/job/{hash_id}/status`) instead. Its answers say so in the `Deprecation` and `X-YoPrint-Successor` headers.

Retired. This v1 route validates the body, then always fails with HTTP 500 and the bare body `{ "message": "Server Error" }` (the deprecation text is not shown in production). Nothing changes. Use Change a job's status on the v2 API.

## Path parameters

- `team_slug` (string, required): Your team slug, shown as Team ID next to your API key in Profile. Example `your-team`.
- `hash_id` (string, required): The job's hash id (`id`). Hash ids only: a unique key or a document number gives 404. Example `WaGvtaWsx7Kcn4`.

## Request body

Content type `application/json`, required.

Fields:

- `status_id` (string, required): A job status hash id.
- `notify_customer` (boolean | null, optional): Accepted and ignored.

### Example request

```bash
curl -X PUT 'https://secure.yoprint.com/v1/api/store/your-team/job/WaGvtaWsx7Kcn4/status' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1' \
  -H 'Content-Type: application/json' \
  -d '{
    "status_id": "scaWHQnPLtqMPT"
  }'
```

## Response

`200` Never sent: this retired route always fails with HTTP 500.

No response body.

## 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.
  - When: The id is not one of your team's hash ids (checked first). Fix: Use the v2 route.
- `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: `status_id` is missing or not a hash id. Fix: Send a job status hash id.
- `500` A business rule refused the request (see the operation's errors), or something failed inside YoPrint. Refusals use the error envelope with a code such as `action_not_allowed`; an unexpected failure answers `{"message": "Server Error"}`. Repeating a refusal gets the same answer; after an unexpected failure, read the record back before you retry a change.
  - When: Always, after validation, as `{ "message": "Server Error" }`. Nothing changes. Fix: Call `PUT /v2/job/{hash_id}/status` instead.

## Related

- [Change a job's status](https://developer.yoprint.com/reference/jobs/v2-job-change-status.md): `PUT /v2/api/store/{team_slug}/v2/job/{hash_id}/status`