Absence.io
Absence.io is an innovative and efficient leave management software that simplifies the process of tracking and managing employee absences. It provides a centralized platform for both employees and managers to easily request, approve, and track time-off requests. Absence.io helps streamline communication and ensure transparency within an organization by providing real-time updates on employee availability and leave balances. The REST API v2 allows integration with absences, users, allowances, departments, locations, reason types, and timespans using Hawk authentication.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Absence.io the way a machine reads it — 56 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Absence.io scores 60.1/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Absence.io
Each block below is one kind of artifact we hold for Absence.io. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Absence.io Absences API
Operations for managing employee absence records.
Absence.io Allowances API
Operations for managing employee leave allowances and balances.
Absence.io Departments API
Operations for retrieving organizational department information.
Absence.io Locations API
Operations for retrieving office location information.
Absence.io Reason Types API
Operations for retrieving absence reason type definitions.
Absence.io Timespans API
Operations for retrieving working time configurations.
Absence.io Users API
Operations for retrieving user/employee information.
Scroll within the panel for all 7 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Absence.io API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Absence Io Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Absence Io Finops
FINOPSFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Absence Management
Create, approve, and track employee vacation, sick leave, and other absence types through a centralized platform.
Leave Allowances
Configure and track annual leave allowances per employee, including carryover management.
Approval Workflows
Configurable approval workflows for absence requests with manager notifications and audit trail.
Organizational Structure
Support for departments, locations, and teams to reflect your organization's hierarchy.
Reason Types
Customizable absence reason types (vacation, sick leave, parental leave, etc.) with color coding.
Working Time Configurations
Define timespans with hours per day and days per week for accurate absence calculation.
REST API v2
Full REST API for integrating absence management with ERP, HRIS, and other business systems using Hawk authentication.
Scroll within the panel for all 7 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Absence Io Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Absence.io API Rules
SPECTRALAbsence.io API Rules
SPECTRALJSON Schema 7
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Absence
JSON SCHEMAAllowance
JSON SCHEMADepartment
JSON SCHEMALocation
JSON SCHEMAReasonType
JSON SCHEMATimespan
JSON SCHEMAUser
JSON SCHEMAScroll within the panel for all 7 ·
JSON Structure 7
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Absence Structure
JSON STRUCTUREAllowance Structure
JSON STRUCTUREDepartment Structure
JSON STRUCTURELocation Structure
JSON STRUCTUREReason Type Structure
JSON STRUCTURETimespan Structure
JSON STRUCTUREUser Structure
JSON STRUCTUREScroll within the panel for all 7 ·
Examples 7
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Absence Example
EXAMPLEAllowance Example
EXAMPLEDepartment Example
EXAMPLELocation Example
EXAMPLEReason Type Example
EXAMPLETimespan Example
EXAMPLEUser Example
EXAMPLEScroll within the panel for all 7 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
ERP Integration
Integrate absence data with ERP systems to automatically reflect employee availability and costs.
HRIS Sync
Sync employee records between Absence.io and HR information systems to maintain a single source of truth.
Payroll Processing
Use absence and allowance data to calculate accurate payroll deductions and entitlements.
Capacity Planning
Query team absence data to plan project staffing and identify scheduling conflicts.
Absence Reporting
Generate custom reports on absence patterns, allowance usage, and team availability.
Custom Dashboards
Pull absence and allowance data into custom HR dashboards and analytics tools.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Slack
Integration with Slack for absence request notifications and team visibility.
Atlassian Jira
Integration with Jira for project planning with awareness of team availability.
SharePoint
Integration with SharePoint for absence calendar sharing and team visibility.
Google Calendar
Sync absence records to Google Calendar for team scheduling visibility.
Redmine
Integration with Redmine project management for resource planning.
Resources
Every other property we hold for Absence.io — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/absence-io · machine-readable index on apis.io