Client-initiated termination

Step 1: Check restricted offboarding dates

Some countries prohibit terminations on specific dates, such as public holidays or payroll processing windows. Always check restricted dates before submitting a termination request. Use the Retrieve restricted offboarding dates endpoint.

$
curl --location --request GET \
>
  '{{host}}/rest/eor/contracts/{{contract_id}}/offboarding/restricted-dates' \
>
  --header 'Authorization: Bearer {{client_token}}'

The response includes a list of date ranges the client must avoid when setting the last working day. If the proposed termination date falls within a restricted range, Deel rejects the termination request.

Step 2: Retrieve additional required information

Country-specific regulations may require answers to additional questions before a termination can be submitted. Use the Get additional information required to request employee termination endpoint to retrieve those fields.

$
curl --location --request GET \
>
  '{{host}}/rest/eor/contracts/{{contract_id}}/offboarding/required-information' \
>
  --header 'Authorization: Bearer {{client_token}}'

The response describes what fields to include in the termination request body. Always call this endpoint before submitting a termination: required fields vary by country and contract type.

Step 3: Initiate the termination request

Submit the termination request using the Initiate EOR contract termination request endpoint. Include the termination reason, last working day, and any fields returned in the previous step.

$
curl --location --request POST \
>
  '{{host}}/rest/eor/contracts/{{contract_id}}/offboarding/termination' \
>
  --header 'Authorization: Bearer {{client_token}}' \
>
  --header 'Content-Type: application/json' \
>
  --data-raw '{
>
    "data": {
>
      "last_working_day": "2025-09-30",
>
      "termination_reason": "PERFORMANCE",
>
      "additional_information": {}
>
    }
>
  }'

Step 4: Monitor offboarding status

After submitting the termination, poll the offboarding status using the Retrieve Offboarding Request endpoint to track progress through the document preparation and sign-off stages.

$
curl --location --request GET \
>
  '{{host}}/rest/eor/contracts/{{contract_id}}/offboarding' \
>
  --header 'Authorization: Bearer {{client_token}}'

For the full status reference, see Status values below.

Step 5: Retrieve employee time-off data

Before finalizing the offboarding, retrieve the employee’s outstanding time-off balance to ensure accurate final pay calculations. Use the Retrieve Employee Time Off Data for Offboarding endpoint.

$
curl --location --request GET \
>
  '{{host}}/rest/eor/contracts/{{contract_id}}/offboarding/time-offs' \
>
  --header 'Authorization: Bearer {{client_token}}'

Step 6: Review and approve offboarding documents (client sign-off)

Once Deel prepares the offboarding documents, the client must review and approve or request changes. Use the Review, approve, or request changes to EOR offboarding documents endpoint.

$
curl --location --request POST \
>
  '{{host}}/rest/eor/contracts/{{contract_id}}/offboarding/review-client-sign-offs' \
>
  --header 'Authorization: Bearer {{client_token}}' \
>
  --header 'Content-Type: application/json' \
>
  --data-raw '{
>
    "data": {
>
      "approved": true
>
    }
>
  }'

Step 7: Submit employee sign-off review

After the employee has reviewed their offboarding documents, submit the employee sign-off review on behalf of the organization using the Submit employee sign-off review for offboarding documents endpoint.

$
curl --location --request POST \
>
  '{{host}}/rest/eor/contracts/{{contract_id}}/offboarding/review-employee-sign-offs' \
>
  --header 'Authorization: Bearer {{client_token}}' \
>
  --header 'Content-Type: application/json' \
>
  --data-raw '{
>
    "data": {
>
      "approved": true
>
    }
>
  }'