# Delete a shipping method

```http
DELETE https://secure.yoprint.com/v1/api/store/{team_slug}/setting/shipping_type/{hash_id}
```

- API version: v1
- Operation ID: `v1_public_shipping_type_destroy`
- Section: Team settings › [Shipping methods](https://developer.yoprint.com/reference/shipping-methods.md)
- Web page: https://developer.yoprint.com/reference/shipping-methods/v1-shipping-type-destroy/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

Deletes a shipping method. It stays in the list with `trashed: true` and can be restored. Shipments that used it keep it.

## Permission

Needs the Manage Settings permission.

## Business rules

- The default method, and the GoShippo and Shopify fulfillment methods, cannot be deleted.

## 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 shipping method's `id`: a hash id from an earlier answer. Only hash ids work here; anything else answers 404 `page_not_found`. Example `1aNKrP6pU0uytN`.

## Request body

This operation takes no request body.

### Example request

```bash
curl -X DELETE 'https://secure.yoprint.com/v1/api/store/your-team/setting/shipping_type/1aNKrP6pU0uytN' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1'
```

## Response

`200` Successful response.

Fields:

- `data` (null, required)
- `status` (integer, required)
- `success` (boolean, required)

Example response:

```json
{
  "data": null,
  "status": 200,
  "success": true
}
```

## Errors

- `401` The API key is missing or wrong (`unauthenticated`).
  - When: The API key is missing or wrong. Fix: Send your personal API key as `Authorization: Bearer YOUR_API_KEY`.
- `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`.
  - When: Your permission group lacks Manage Settings. This 403 has a short body, `{"message": "Insufficient Permission"}`, without `success` or `error`. Fix: Ask the team owner to give your permission group Manage Settings.
- `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: No shipping method with that id on this team (`error.code` is null and `error.message` starts "No query results"), the id is not one of this team's hash ids, or you are not a member of the team (both `page_not_found`). Fix: Use an `id` from the list operation and check the team slug.
- `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: The method is the default, or a GoShippo or Shopify fulfillment method (`error.code` is `delete_fail`). Fix: Make another method the default first. YoPrint's own methods stay.

## Related

- [Restore a shipping method](https://developer.yoprint.com/reference/shipping-methods/v1-shipping-type-restore.md): `PATCH /v1/api/store/{team_slug}/setting/shipping_type/{id}/restore`