> 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/absence/absence-types.md). # Absence types When working with absences in SameSystem, an absence can generally be a **one-day absence** or marked as **period absence**. ### One-Day Absence A one-day absence covers a single day. The **start date and end date are the same**. Typical examples include: * A single sick day. * One day of holiday. * Other single-day absences. * Few hours of absence. ### Period Absence A period absence covers multiple consecutive days and therefore has a **different start and end date**. Typical examples include: * Maternity or parental leave * Long-term sickness * Longer holiday periods * Other extended leave When integrating absence data, make sure to use the appropriate absence type based on whether the absence covers a single day or a period of multiple days. Use the regular absence endpoint (API v1) for single-day absences and the period absence endpoints (API v2) for absences covering a date range, such as maternity leave, leave of absence, or long-term sickness. Absence logs are only present in API v2. --- # 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/absence/absence-types.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.