> 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/data-models/contract/plus-agreements.md). # Plus agreements {% hint style="info" %} Only available in API v2. {% endhint %} Plus agreements are additional work arrangements linked to an existing contract. Each Plus agreement has its own period (start- and end date) and hours.

Plus agreements are linked to a contract. You can have multiple Plus agreements under each contract. {% hint style="info" %} **Prerequisite:** Plus agreements must be enabled for the client. **General settings - Employees tab - Plus agreements checkbox.** {% endhint %} ### Fields The fields related to Plus agreements:


`contractId`	An internal (SameSystem) id to the contract that is linked to the Plus agreement.
`contractType`	Can be one of the following values: `FIXED_TERM`, `PERMANENT`, `SEASONAL, TEMPORARY`, `AGREED_FIXED_TIME`, `NOT_EMPLOYED`, `PROBATIONARY_EMPLOYMENT`
`startDate`	This is the start date for the Plus agreement and will be the date when the Plus agreement will be active.
`endDate`	This is the end date for the Plus agreement and will be the last date the Plus agreement is active.
`id`	An internal (SameSystem) id to the Plus agreement.
`note`	Note regarding the Plus agreement.
`status`	Can be one of the following values: `ACTIVE`, `EXPIRED`, `UPCOMING`
`hoursWeek`	The number of hours per week for this Plus agreement. It is the work hours per week for every week the Plus agreement is active.
`addtionalHours`	The number of additional hours for this Plus agreement. This means the total number of hours in the whole Plus agreement period. Currently the `additionalHours` is used when a Plus agreement is shorter than 7 days.

Normally you would use either hoursWeek or additionalHours. --- # 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/data-models/contract/plus-agreements.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.