> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clustr-ai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete Owner

> Remove an owner and unassign their opportunities

Remove a person from the owner directory.

Every opportunity owned by that person becomes unowned. The opportunities are not deleted and nothing else about them changes, they simply end up with no owner, exactly as if you had unassigned each one by hand. The response reports how many opportunities that was, so you can reassign them.

<Warning>
  This cannot be undone. Reassigning the opportunities afterwards is a manual step.
</Warning>

## Path Parameters

<ParamField path="id" type="string" required>
  Owner UUID. Use [List Owners](/api-reference/list-owners) to find it.
</ParamField>

## Response Fields

<ResponseField name="unassigned_opportunities" type="integer">
  How many opportunities were left with no owner by this delete.
</ResponseField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X DELETE "https://api.clustr-ai.com/api/public/owners/9c8e77d1-4b2a-4c8f-9a30-6e21d4f0aa57" \
    -H "Authorization: Bearer YOUR_API_KEY"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "success": true,
    "data": {
      "unassigned_opportunities": 3
    }
  }
  ```

  ```json 404 theme={null}
  {
    "success": false,
    "error": { "message": "Owner not found", "code": "NOT_FOUND" }
  }
  ```

  ```json 401 theme={null}
  {
    "success": false,
    "error": { "message": "Invalid or missing API key", "code": "UNAUTHORIZED" }
  }
  ```
</ResponseExample>