> 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/new-employees/hire-future-employee.md).
# Hire future employee
{% hint style="info" %}
**Note:** Users can also be created using **API v1**. However, for user and contract integrations, we strongly recommend using **API v2**, and this guide therefore describes user creation using API v2 only.
If you need to create users using API v1, please refer to the [**API v1 OpenAPI specification**](https://docs.samesystem.dev/api-v1-reference/) for the available endpoint, request parameters, and data model.
{% endhint %}
A new employee with a future start date will require a new user and a new contract from the start date. You can create the user immediately and create a contract with the future start date. The new employee becomes active on the start date.
You will have the following options to create the records:
Create user and contract in two separate calls
To create a user first and then create a contract afterwards, the following endpoints can be used:
POST /{clientToken}/users\
POST /{clientToken}/users/{userId}/contracts/insert
Create user and contract in a single call
To create both the user and the contract in a single call, the following endpoint can be used:
POST /{clientToken}/users/create\_with\_contract
Create/update multiple users and contracts in one call (bulk update/create)
To create and/or update multiple users with contract in a single call from a payroll or HR system with the use of a custom id (external user id), the following endpoint can be used:
POST /{clientToken}/users/upsert\_with\_contracts
Request body is an array of objects conforming to the `UsertUsersWithContractInput` schema. Each object in the array has a required `externalUserId` and two objects. These two objects conform with the `CreateUserWithContractUserInput` schema for the user data and the `CreateUserWithContractContractInput` for the contract data.
**How to choose?**
If you need to create multiple users and contracts from an HR-system in a daily scheduled run and you have all information about users and contracts, it could be an idea to create all users and contracts in one call.
If you want to create the user as soon as possible (before you have contract information), you can start to create the user in one call. Later, when the contract details are ready, you can create the contract in another call.
If you have both user and contract details ready to start with, you can combine the creation of the user and contract in one call.
---
# 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/new-employees/hire-future-employee.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.
