> For the complete documentation index, see [llms.txt](https://docs.samesystem.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samesystem.dev/business-guides/employee-lifecycle-management/terminate-employees/remove-termination.md).
# Remove termination
{% hint style="info" %}
Only available in API v2.
{% endhint %}
In this scenario, the user has been terminated with a future end date. If you decide to cancel the termination, you can remove it before the termination date.
The user will continue to be active with the current contract. The termination date will be removed.
You will have this option to remove the termination of the employment:
Remove termination
To remove a termination date for a user in a single call, the following endpoint can be used:
POST /{clientToken}/users/{id}/remove\_termination
The parameter `{id}` is the unique id number of the user in SameSystem. The value is present in the user object: `user.id`. \
It can also be a custom Id, like an employee id or payroll number from an external system. If a custom id is used, you must include the parameter `useCustomId=true` in the call.
Request body is empty.
{% hint style="info" %}
**Notice:**
Removing termination date on a contract triggers background jobs that synchronize/clean-up the user’s calendar lines in the system. While these jobs are running, the user is temporarily marked as updating and contract creation/updating are blocked during the update process.
To make the integration resilient to this, we recommend a retry with backoff if you need to add changes to the contract again.
Example: Add a retry once after 5 seconds, then 30 seconds, and then one minute rather than assuming the endpoint will always be immediately available.
{% endhint %}
After you remove the termination, the user and contract will be updated, and the employment end date will be removed.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.samesystem.dev/business-guides/employee-lifecycle-management/terminate-employees/remove-termination.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
