Skip to main content
DELETE
Delete Workforce Employee
← Own Workforce API
Deprecated. Use POST /v2/own-workforce/employees/delete: many employees per request by id, idempotent, deleted asynchronously as an ingest job, with webhooks. This endpoint keeps working; its responses carry Deprecation and Link: </v2/own-workforce/employees/delete>; rel="successor-version" headers. Its responses also carry Sunset: Fri, 30 Apr 2027 00:00:00 GMT: the endpoint is retired on April 30, 2027 (see the changelog).
Delete a single employee. This is irreversible, and there is no endpoint that creates one back — the only way to restore an employee is to re-import them through the Imports API.
Deleting an employee removes the records that depend on them: contracts, remunerations, trainings and absence/accident records. Their reported headcount, FTE and training hours change accordingly for every period they appeared in.

Request

Headers

string
required
Your API key for authenticationExample: sk_live_1234567890abcdef
string
required
Your organization UUIDExample: a8315ef3-dd50-43f8-b7ce-d839e68d51fa

Path Parameters

string
required
Employee UUIDExample: 550e8400-e29b-41d4-a716-446655440000

Response

204 No Content with an empty body.

Example

Common Errors

401 Unauthorized

Cause: the key is invalid or revoked (INVALID_API_KEY), expired (API_KEY_EXPIRED), belongs neither to the organization in x-organization-id nor to one of its parents (API_KEY_ORG_MISMATCH), or has no owner (API_KEY_NO_OWNER). A request carrying no credentials at all answers AUTHENTICATION_REQUIRED. See Errors.

403 Forbidden

Cause: the key’s owner is not an enabled member of the organization in x-organization-id, or the key’s role cannot write.

404 Not Found

Cause: no employee with that id inside your perimeter. A row owned by an organization outside the header organization’s accepted family answers 404, never 403.

Bulk delete employees

Delete up to 100,000 by id

Bulk delete by filters

Delete everything a filtered list returned