Rentals
Contract
Rental contract.
Schemas: ContractDto
Example
Generated from the schema
A rental contract with its document status (status) and its signature status (operativeStatus), which move separately: validating a contract does not sign it. It points to the order, the contact and the project it belongs to. The legal clauses and the tax snapshot of the customer are not published. Contracts are bounded to the subscription that owns the key.
Attributes
Unique contract identifier.
Contract number, for example "C260001"; null while it is a draft.
Document status.
Available options: draft, validated, voided
Signature status.
Available options: pending, signed, cancelled
true if the contract is recorded as signed. This is what decides whether the equipment can go out.
Signature date in ISO 8601 UTC; null if not signed.
Customer identifier; null in drafts without a customer.
Associated order; null if it has none.
Number of the associated order; null if it has none.
Associated project; null if it has none.
Contract date in ISO 8601 UTC; null if not set.
Start of validity in ISO 8601 UTC; null if not applicable.
End of validity in ISO 8601 UTC; null if not applicable.
Total amount including taxes as a decimal string "1234.50"; null if not applicable.
Limits: pattern ^-?\d+\.\d{2}$
Creation date in ISO 8601 UTC; null if not recorded.
Last modification date in ISO 8601 UTC; null if not recorded.
Values
- status
draft,validated,voided- operativeStatus
pending,signed,cancelled
Returned by
GET /api/v1/contracts— List contractsGET /api/v1/contracts/{contractId}— Get a contract
Modified by
POST /api/v1/contracts/{contractId}/validate— Validate a contractPOST /api/v1/contracts/{contractId}/sign— Record the signature of a contractPOST /api/v1/contracts/{contractId}/void— Void a contractPOST /api/v1/contracts/{contractId}/cancel— Cancel a contract operatively
Was this page helpful?