# Delete a customer contact

```http
DELETE https://secure.yoprint.com/v1/api/store/{team_slug}/customer/{hash_id}/contact/{id}
```

- API version: v1
- Operation ID: `v1_public_customer_contact_destroy`
- Section: Customers › [Customer contacts](https://developer.yoprint.com/reference/customer-contacts.md)
- Web page: https://developer.yoprint.com/reference/customer-contacts/v1-customer-contact-destroy/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

Deletes a contact. It can be restored. Documents that already name it keep it. The primary contact can't be deleted: make another contact primary first.

## Permission

Needs the Manage Customers permission ("Manage All" or "Manage Assigned to User"). Whether the customer is assigned to you is not checked.

## Business rules

- Customers synced from Shopify are read-only here: changes are refused with 422 `validation_error` "External customers are read-only. Manage changes from Shopify." System customers (`is_system: true`) are refused the same way ("System customer cannot be modified or deleted.").
- Contacts synced from Shopify are read-only (422).

## Side effects

- Sends the `customer_contact.deleted` webhook.
- Removes the Customer Portal access the contact gave for this customer, and any access denial with it. When the portal account then has no active access to any customer, its signed-in sessions end. The account and its access to other customers stay.

## 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 customer's id (`id` from List customers or Create a customer). A hash id from an earlier answer; unique keys and document numbers (such as `PO0042`) don't work here. Example `EDhVUaC6jbLbed`.
- `id` (string, required): The contact's id (`id` from List a customer's contacts, or from List a vendor's contacts). A hash id from an earlier answer; unique keys and document numbers (such as `PO0042`) don't work here. Example `uAu3dAKIaHyAYk`.

## Request body

This operation takes no request body.

### Example request

```bash
curl -X DELETE 'https://secure.yoprint.com/v1/api/store/your-team/customer/EDhVUaC6jbLbed/contact/uAu3dAKIaHyAYk' \
  -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`).
- `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 role has no Manage Customers permission. This 403 has a short body, `{"message": "Insufficient Permission"}`, with no `success` or `error`. Fix: Ask a team owner to give your role Manage Customers.
- `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 contact is already deleted, or belongs to another customer. `error.code` is null and `error.message` names the record type. Fix: Check the ids.
- `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: The customer comes from Shopify, or is a system customer (`error.code` `validation_error`, with the reason in `error.message`). Fix: Change Shopify customers in Shopify. System customers cannot be changed.
- `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 contact is the primary contact. This route answers HTTP 500 with `error.code` `delete_fail` and `error.message` null; nothing is deleted. Fix: Set another contact as primary, then delete this one. Don't retry the same call: it fails the same way.

## Related

- [Restore a deleted customer contact](https://developer.yoprint.com/reference/customer-contacts/v1-customer-contact-restore.md): `PATCH /v1/api/store/{team_slug}/customer/{hash_id}/contact/{id}/restore`
- [Set the primary contact](https://developer.yoprint.com/reference/customer-contacts/v1-customer-contact-primary.md): `PATCH /v1/api/store/{team_slug}/customer/{hash_id}/contact/{id}/primary`