Skip to main content
POST
Bulk Delete Workforce Employees
← Own Workforce API Delete up to 100,000 employees in one call by listing their ids. The response reports what succeeded and what did not, so a partial failure is visible rather than silent.
Irreversible, and it cascades: each deleted employee takes their contracts, remunerations, trainings and absence records with them. There is no create endpoint to put them back — only a re-import.

Request

Headers

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

Body

array[string]
required
Employee UUIDs to delete. Between 1 and 100,000 entries.
boolean
default:"false"
Group view. false authorizes deletion inside the header organization only. true authorizes it across the whole accepted family.Ids outside the resolved perimeter are never deleted; they come back in failed_ids instead.

Response

integer
How many employees were deleted
array[string]
Ids of the deleted employees
integer
How many ids were not deleted — unknown, already gone, or outside your perimeter
array[string]
Ids that were not deleted
string
Human-readable summary
The call returns 200 OK even when some ids fail. Always read failed_count rather than relying on the status code.

Example

Successful Response

Common Errors

401 Unauthorized

Cause: the key is invalid, or it does not belong to the organization in x-organization-id — the two are looked up as a pair. A request carrying no credentials at all answers AUTH_REQUIRED instead.

403 Forbidden

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

422 Unprocessable Entity

Cause: empty own_workforce_ids, more than 100,000 entries, or a value that is not a UUID.

Bulk delete by filters

Delete what a filtered list returned, without collecting ids

Delete one employee

Single-record deletion