# DELETE /api/v2/customers/{customer}

Delete a customer

- MCP id: customers.destroy
- Scope: api:destroy:customers
- Permission: customers::delete
- Rate cost: 1 unit, write bucket.
- Cache-Control: private, no-store

Soft-deletes a customer and returns `204`; `POST customers/{customer}/actions/restore` reverses it.

The DELETE cascades to projects: a soft delete also soft-deletes every project of this customer, and actions/restore does not bring them back; restore each one through `POST projects/{project}/actions/restore`. There is no permanent delete: `force=true` answers `400` `unsupported-parameter`. Deleting an already-deleted customer answers `204`, so a retry is safe.

## Parameters
- customer (integer, path): The Customer's numeric id. Accepts a soft-deleted record.
- X-Request-Id (header, optional): A correlation id of your own. It is recorded in our logs next to the server's request id but never returned: the response header always carries the server's id. A value that does not match the pattern is discarded silently, never rejected.
- If-Match (header, optional): The ETag a write is conditional on. A stale validator is 412 precondition-failed.

## Response 204

## Errors
- 403 forbidden-by-policy | insufficient-permission | insufficient-token-scope: Forbidden.
- 412 precondition-failed: Precondition failed.
- 400 idempotency-key-required | invalid-cursor | invalid-query-parameter | malformed-request | unsupported-parameter: Bad request.
- 401 token-expired | unauthenticated: Unauthenticated.
- 404 endpoint-not-found | resource-not-found: Not found.
- 406 not-acceptable: Not acceptable.
- 429 rate-limit-exceeded: Too many requests.
- 500 internal-error: Server error.
- 503 tenant-unavailable: Service unavailable.

## Example
```bash
curl -X DELETE \
  'https://<your-url>/api/v2/customers/1' \
  -H 'Authorization: Bearer <token>' \
  -H 'Accept: application/json'
```