# Delete all shipments of an order (retired)

```http
PATCH https://secure.yoprint.com/v2/api/store/{team_slug}/v2/sales_order/{hash_id}/shipment/delete_all
```

- Status: legacy, deprecated
- API version: v2
- Operation ID: `v2_public_sales_order_shipment_destroy_all`
- Section: Shipping › [Shipments](https://developer.yoprint.com/reference/shipments.md)
- Web page: https://developer.yoprint.com/reference/shipments/v2-sales-order-shipment-destroy-all/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

> **Legacy (deprecated).** A newer operation does this better: use [Delete a shipment](https://developer.yoprint.com/reference/shipments/v2-shipment-destroy.md) (`DELETE /v2/api/store/{team_slug}/v2/shipment/{unique_key}`) instead. Its answers say so in the `Deprecation` and `X-YoPrint-Successor` headers.

Retired: this operation does nothing and always answers with the error code `depcreated` (HTTP 500). Delete shipments one at a time instead. `{hash_id}` is the order's `id` (for example `V4keXwwxMQyXw7`); the `ord_` unique key is not accepted here.

## Permission

Any member of the team.

## 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 sales order's or quote's `id` (a hash id). The `ord_` unique key and the order number do not work here. Example `V4keXwwxMQyXw7`.

## Request body

This operation takes no request body.

### Example request

```bash
curl -X PATCH 'https://secure.yoprint.com/v2/api/store/your-team/v2/sales_order/V4keXwwxMQyXw7/shipment/delete_all' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1'
```

## Response

`200` Never sent: this 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.
- `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: `{"status": 500, "success": false, "error": {"code": "depcreated", "message": null}}`. Fix: Delete each shipment with Delete a shipment.

## Related

- [Delete a shipment](https://developer.yoprint.com/reference/shipments/v2-shipment-destroy.md): `DELETE /v2/api/store/{team_slug}/v2/shipment/{unique_key}`