Employment Management

employment.hard_deleted

This event is triggered when an employment is permanently erased from Remote, and means the record is physically gone: a subsequent GET /employments/{id} returns 404 and the identifier must not be queried again.

An employment that is hard deleted has often already been soft deleted, which triggered employment.onboarding.cancelled. You may therefore receive employment.onboarding.cancelled first and this event weeks later.

This event may be delivered more than once, so it is safe to process repeatedly.

postWebhookemployment.hard_deleted

Payload

company_idstring required

The unique identifier of the related company.

employment_idstring required

The unique identifier of the related employment.

event_typestring required

The webhook event type identifier.

hard_deleted_atstring date-time required

The UTC timestamp at which the employment was erased.

Example payload

{
  "company_id": "d2091b1e-b1a4-437a-91ea-2809ffbb6d59",
  "employment_id": "102172fe-4e09-480c-bd70-09cfeb34022a",
  "event_type": "employment.hard_deleted",
  "hard_deleted_at": "2026-08-24T11:02:31Z"
}

Response

Any 200 response confirms that the webhook was delivered.

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.