---
title: "Create Offboarding"
method: POST
path: "/v1/offboardings"
tags: ["Terminations"]
---

# Create Offboarding

`POST /v1/offboardings`

Creates an Offboarding request


## Scopes

| Category | Read only Scope | Write only Scope (read access implicit) |
|---|---|---|
| Manage employments (`employments`) | - | Manage offboarding (`offboarding:write`) |

## Request body

- CreateOffboardingParams
  - `employment_id` string, required — The unique identifier (UUID) of the employment to be terminated.
  - `termination_details` TerminationDetailsParams, required
    - `acknowledge_termination_procedure` boolean, nullable — Whether the employer acknowledges and agrees to follow Remote's termination procedure for this jurisdiction.
    - `additional_comments` string, nullable — Additional details regarding the termination process.
    - `agrees_to_pto_amount` boolean, nullable — Whether the employer agrees with the employee's current paid time off balance. If false, you may provide a timesheet file documenting any discrepancies.
    - `agrees_to_pto_amount_notes` string, nullable — Additional notes about the PTO balance, especially if there are discrepancies.
    - `confidential` boolean, required — Confidential requests are visible for who authorized the token or integration. Non-confidential requests are visible to all admins in the company.
    - `customer_informed_employee` boolean, nullable — Whether the employer has already informed the employee about the termination. Remote advises not informing the employee until the request has been reviewed for legal risks.
    - `employee_awareness` object — Remote advises not to inform the employee of their termination until we review your request for legal risks. When we approve your request, you can inform the employee and we’ll take it from there. This field is only required if employee was informed before creating the offboarding request.
      - `date` string, date, nullable — When the employee was told about the termination.
      - `note` string, nullable — Notes describing how the termination was shared with the employee. Remote advises being as specific as possible, and include details about the employee’s response, if applicable.
    - `personal_email` string, email — Remote will use this email address for post-termination communication. If it is not provided, this field will be derived from the employment record. Therefore, it is important to ensure that it is not a company email.
    - `proposed_termination_date` string, date, required — In most cases, employee needs to be notified before termination. The required notice period depends on local labor laws, the employment agreement, and other factors. Remote will use those factors to determine the required notice period. Please note that we cannot commit to a termination date until we conduct a full review of the information you submit.
    - `reason_description` string, required — Description of the reason for termination
    - `risk_assessment_reasons` string[], required — Possible reasons for offboarding risk assessment
    - `termination_reason` 'cancellation_before_start_date' | 'compliance_issue' | 'conversion_to_contractor' | 'dissatisfaction_with_remote_service' | 'end_of_fixed_term_contract_compliance_issue' | 'end_of_fixed_term_contract_incapacity_to_perform_inherent_duties' | 'end_of_fixed_term_contract_local_regulations_max_term_reached' | 'end_of_fixed_term_contract_misconduct' | 'end_of_fixed_term_contract_operational_reasons' | 'end_of_fixed_term_contract_other' | 'end_of_fixed_term_contract_performance' | 'end_of_fixed_term_contract_redundancy' | 'end_of_fixed_term_contract_values' | 'gross_misconduct' | 'incapacity_to_perform_inherent_duties' | 'job_abandonment' | 'mutual_agreement' | 'other' | 'performance' | 'values' | 'workforce_reduction', required — Choose an accurate termination reason to avoid unfair or unlawful dismissal claims. If the termination is created before the employee's start date, this field will be set to `cancellation_before_start_date`.
    - `termination_reason_files` OffboardingFile[] — Any supporting documents regarding the termination reason
      - `content` string, binary, required — The content in base64 encoding
      - `name` string, required — The file name
    - `timesheet_file` OffboardingFile
      - `content` string, binary, required — The content in base64 encoding
      - `name` string, required — The file name
    - `will_challenge_termination` boolean, required — Whether is it likely or not that the employee will challenge their termination
    - `will_challenge_termination_description` string — If it is likely that the employee will challenge their termination, please provide additional details explaining the risk
  - `type` 'termination', required — The type of the offboarding request. For now, only `termination` is allowed.

## Response `201`

Success

- OffboardingResponse — Response containing a single offboarding record with full details.
  - `data` Offboarding — A wrapper containing an offboarding record, which can be either a termination (employer-initiated) or a resignation (employee-initiated).
    - `offboarding` union
      - object — An offboarding request initiated by the employee (a resignation). Includes the employee's proposed last working day, reason, and status tracking through Remote's process.
        - `additional_comments` string, nullable — Additional comments or context about the resignation.
        - `agrees_to_pto_amount` boolean — Whether the employer agrees with the employee's PTO balance.
        - `employer_awareness` string — A description of how and when the employer was made aware of the resignation.
        - `employment_id` string, required — The unique identifier (UUID) of the employment being resigned from.
        - `id` string, required — The unique identifier (UUID) of the offboarding request.
        - `offboarding_id` string, nullable — The unique identifier (UUID) of the offboarding record. When present, this can be used to query `GET /api/eor/v2/offboardings/{id}` for the v2 offboarding shape.
        - `proposed_last_working_day` string, date, required — The employee's proposed last working day. The actual last day may differ based on notice period requirements.
        - `reason_description` string — A detailed description of the employee's reason for resigning.
        - `requested_by` string, required — The unique identifier (UUID) of the employee who submitted the resignation.
        - `resignation_reason` 'cancellation_before_start_date' | 'company_culture_or_values' | 'conversion_to_contractor' | 'conversion_to_global_payroll' | 'conversion_to_peo' | 'dissatisfaction_with_remote_service' | 'incapacity_to_perform_inherent_duties' | 'infrastructure_challenges' | 'lack_of_recognition' | 'leadership' | 'mutual_agreement' | 'other' | 'other_job_opportunity' | 'personal_reasons' | 'position_does_not_meet_expectations' | 'relationship_with_coworkers' | 'relocation_from_entity_to_entity_by_employee' | 'relocation_leaving_remote' | 'remuneration_and_benefits' | 'retirement' | 'transfer_and_relocation_new_customer_and_new_country' | 'transfer_between_remote_customer' | 'transfer_from_remote_to_customer' | 'transfer_from_remote_to_other_eor', required — The reason the employee gave for their resignation.
        - `status` 'submitted' | 'in_review' | 'done' | 'canceled', required — The current status of the offboarding request. - `submitted`: The resignation has been submitted and is awaiting review. - `in_review`: Remote is processing the resignation. - `done`: The offboarding has been completed. - `canceled`: The resignation was withdrawn or canceled.
        - `submitted_at` string, datetime, required — The timestamp when the resignation was submitted.
        - `termination_date` string, date, nullable, required — Most updated termination date for the offboarding. This date is subject to change through the offboarding process even after it is finalized.
        - `type` 'resignation', required — The type of offboarding. Always `"resignation"` for employee-initiated resignations.
      - object — An offboarding request initiated by the employer to terminate an employment. Includes termination details, risk assessment, and status tracking through Remote's review process.
        - `additional_comments` string, nullable, required — Additional comments or context about the termination provided by the employer.
        - `agrees_to_pto_amount` boolean — Whether the employer agreed with the employee's PTO balance at the time of the termination request.
        - `confidential` boolean, required — Whether this offboarding request is confidential. Confidential requests are only visible to the user who authorized the token or integration; non-confidential requests are visible to all company admins.
        - `employee_awareness` object — Details about whether and when the employee was informed about their termination. Only present if the employee was informed before the offboarding request was submitted.
          - `date` string, date, nullable — The date when the employee was told about the termination.
          - `note` string, nullable — Notes about how the termination was communicated to the employee.
        - `employment_id` string, required — The unique identifier (UUID) of the employment being terminated.
        - `id` string, required — The unique identifier (UUID) of the offboarding request.
        - `offboarding_id` string, nullable — The unique identifier (UUID) of the offboarding record. When present, this can be used to query `GET /api/eor/v2/offboardings/{id}` for the v2 offboarding shape.
        - `personal_email` string, email — Remote will use this email address for post-termination communication. If it is not provided, this field will be derived from the employment record. Therefore, it is important to ensure that it is not a company email.
        - `proposed_termination_date` string, date, required — The employer's proposed termination date. The actual termination date may differ based on local labor laws and notice period requirements.
        - `reason_description` string, required — A detailed description of the circumstances leading to the termination.
        - `requested_by` string, required — The unique identifier (UUID) of the company admin who submitted the termination request.
        - `risk_assessment_reasons` string[], required — Reasons that may increase the legal risk of this termination (e.g., the employee is pregnant, on family leave, etc.).
        - `status` 'submitted' | 'in_review' | 'done' | 'canceled', required — The current status of the offboarding request. - `submitted`: The request has been submitted and is awaiting review by Remote. - `in_review`: Remote is reviewing the request for legal compliance and risks. - `done`: The offboarding has been completed and the employment is terminated. - `canceled`: The offboarding request was canceled before completion.
        - `submitted_at` string, datetime, required — The timestamp when the offboarding request was submitted.
        - `termination_date` string, date, nullable, required — Most updated termination date for the offboarding. This date is subject to change through the offboarding process even after it is finalized.
        - `termination_reason` 'cancellation_before_start_date' | 'compliance_issue' | 'conversion_to_contractor' | 'dissatisfaction_with_remote_service' | 'end_of_fixed_term_contract_compliance_issue' | 'end_of_fixed_term_contract_incapacity_to_perform_inherent_duties' | 'end_of_fixed_term_contract_local_regulations_max_term_reached' | 'end_of_fixed_term_contract_misconduct' | 'end_of_fixed_term_contract_operational_reasons' | 'end_of_fixed_term_contract_other' | 'end_of_fixed_term_contract_performance' | 'end_of_fixed_term_contract_redundancy' | 'end_of_fixed_term_contract_values' | 'gross_misconduct' | 'incapacity_to_perform_inherent_duties' | 'job_abandonment' | 'mutual_agreement' | 'other' | 'performance' | 'values' | 'workforce_reduction', required — The reason for the termination, as submitted by the employer.
        - `type` 'termination', required — The type of offboarding. Always `"termination"` for employer-initiated terminations.
        - `will_challenge_termination` boolean, required — Whether the employer believes the employee is likely to challenge their termination.
        - `will_challenge_termination_description` string — Additional details about why the employee may challenge the termination, if applicable.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `404` — Not Found
- `422` — Unprocessable Entity
- `429` — Too many requests
- `500` — Internal Server Error

---

[API](https://skmtc.net/remote-com/apis/remote.md) · [All operations](https://skmtc.net/remote-com/apis/remote/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/remote-com/remote/revisions/7e6a0c61ac82/schema)