This route is used to create a preventive contract for a specific company. It accept either a duration or an interventionCount, for both, it will estimate the dueAt. It accept a list of site rules ids, and / or routine ids to create the contract.
It is used in the context of creating preventive contracts for companies, allowing the association of site rules and routines.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Session token used for authenticating the request.
"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VySWQiOiIxMjM0NTY3ODkwIiwic2Vzc2lvbklkIjoiYWJjZGVmMTIzNDU2IiwiaWF0IjoxNjA1MDk3ODk5LCJleHAiOjE2MDUxODQyOTl9.4XRQ1iXDyvEj5LgPZHbmTmzOZs98M3YPOzgf3MhxjaI"
Content type, must be "application/json".
application/json Unique identifier of the company.
1
Name of the contract.
250"Service Agreement"
Additional notes or description about the contract.
2500"Annual renewal pending approval."
Reference number of the contract document.
250"Service Agreement"
Duration of the contract in a human-readable format.
x <= 20012
Start date and time of the contract.
"2024-01-15T09:30:00.000Z"
Number of interventions associated with the contract.
5
Unique identifiers of the site rules.
[1, 2, 3]Unique identifiers of the routines.
[1, 2, 3]