Properties
| Name | Type | Description |
|---|---|---|
| _id | string | Unique identifier of the absence. |
| assignedToId | string | ID of the user this absence is assigned to. |
| reasonId | string | ID of the absence reason type. |
| approverId | string | ID of the user who approved this absence. |
| start | string | Start date and time of the absence. |
| end | string | End date and time of the absence. |
| days | number | Number of working days covered by the absence. |
| status | integer | Absence approval status: 0=pending, 1=approved, 2=declined. |
| comment | string | Optional comment or note on the absence. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/absence-io/refs/heads/main/json-schema/absence-schema.json",
"title": "Absence",
"description": "An employee absence record.",
"type": "object",
"properties": {
"_id": {
"type": "string",
"description": "Unique identifier of the absence.",
"example": "500123"
},
"assignedToId": {
"type": "string",
"description": "ID of the user this absence is assigned to.",
"example": "500456"
},
"reasonId": {
"type": "string",
"description": "ID of the absence reason type.",
"example": "500789"
},
"approverId": {
"type": "string",
"description": "ID of the user who approved this absence.",
"example": "500654"
},
"start": {
"type": "string",
"format": "date-time",
"description": "Start date and time of the absence.",
"example": "2025-06-01T00:00:00.000Z"
},
"end": {
"type": "string",
"format": "date-time",
"description": "End date and time of the absence.",
"example": "2025-06-05T23:59:59.999Z"
},
"days": {
"type": "number",
"description": "Number of working days covered by the absence.",
"example": 5
},
"status": {
"type": "integer",
"description": "Absence approval status: 0=pending, 1=approved, 2=declined.",
"example": 1
},
"comment": {
"type": "string",
"description": "Optional comment or note on the absence.",
"example": "Annual leave"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/absence"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.