# deleteEmployee

Delete an AI employee, the employee page's Fire. It is taken off every contact (their schedules go), its mailboxes and lines are released and its forms stop waking it; its history stays, but it cannot be brought back. Admins only: a member is refused, so check getMyProfile's `organizationRole` first and tell a member an organization admin has to fire it. Refused while anything still names it (a workflow step, a saved filter, an automation trigger, an assignment policy); the refusal lists what to change first. Say its contact count (getEmployee's `commitments`). Needs their yes; a card's counts. To stop it for now, switch it off instead (setEmployeeStatus).

- Call: `POST https://server.goliathdata.com/api/v1/call` with `{ "operationId": "deleteEmployee", "variables": {...} }`
- Scope: `WRITE`
- Type: mutation
- Idempotency: honors `Idempotency-Key` (24 h)
- Rate-limited: no

## Variables

- `employeeId`: `ID!` (required)

## Response (data, an example)

```json
{
  "aiEmployeesMutation": {
    "deleteContactAgent": true
  }
}
```

## Example

```bash
curl https://server.goliathdata.com/api/v1/call \
  -H "Authorization: Bearer $GOLIATH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "operationId": "deleteEmployee",
    "variables": {
      "employeeId": "<employeeId>"
    }
  }'
```
