Delete a customer, refused while anything still references them
Remove a customer. Refused with 409 if rows still reference it, naming what holds it.
/v1/customers/{customer_id}Admin- Operation id
- delete_customer
- Access
- An editor or a viewer is refused.
/v1/customers/{customer_id}Remove a customer. Refused with 409 if rows still reference it, naming what holds it.
A customer with tickets cannot be deleted, and the refusal says what is holding them, so the fix is visible rather than guessed. Nothing is cascaded and no ticket is ever removed by this call.
A customer that is not in this workspace answers 404, never 409, so a refusal can never be used to learn that a row exists elsewhere.
There is no response body.
Tenancy: the request is scoped to one workspace, and the credential presented is what selects it. A caller with no membership in that workspace is refused with 404, which is indistinguishable from a workspace that does not exist.
Authorisation: admin or owner. An editor or viewer receives 403 insufficient_role.
Access: Authorization: Bearer carrying either a realm access token or an API key. A key must hold the customers:write scope, and the workspace role of the person who owns it must meet the floor above.
A realm-issued access token, presented as Authorization: Bearer <token>. It acts as the person who signed in, and every operation resolves their workspace role live from the membership record.
In: header
Path Parameters
uuidResponse Body
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/v1/customers/497f6eca-6276-4993-bfeb-53cbbbba6f08"