Leapsome
Leapsome is an AI-powered people enablement platform that combines HRIS, talent management, and HR automation into a single modular solution used by more than 2,000 organizations worldwide. The platform covers the full employee lifecycle including performance reviews, OKRs and goal management, engagement surveys, 1:1 meetings, instant feedback, learning pathways, and compensation management. Leapsome exposes a REST Content API for extracting reviews, goals, employee attributes, payroll, and time-tracking data, plus a SCIM 2.0 API for automated user provisioning and lifecycle management with enterprise identity providers. Both APIs authenticate via bearer tokens generated inside the platform settings and are documented through Swagger UI at api.leapsome.com.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Leapsome the way a machine reads it — 50 machine-readable artifacts across 2 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 — Leapsome scores 48.6/100 (developing), with a separate agent-readiness read of 22/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Leapsome's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/leapsome/"
title="Leapsome on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/leapsome.svg"
alt="Leapsome Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/leapsome/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/leapsome/"
title="Leapsome on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/leapsome/card.svg"
alt="Leapsome Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Leapsome
Each block below is one kind of artifact we hold for Leapsome. 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 14
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.
Leapsome absences API
The absences API from Leapsome — 1 operation(s) for absences.
Leapsome accessRoles API
The accessRoles API from Leapsome — 1 operation(s) for accessroles.
Leapsome auth API
The auth API from Leapsome — 1 operation(s) for auth.
Leapsome documents API
The documents API from Leapsome — 2 operation(s) for documents.
Leapsome feedback API
The feedback API from Leapsome — 4 operation(s) for feedback.
Leapsome goals API
The goals API from Leapsome — 6 operation(s) for goals.
Leapsome Groups API
Operations on groups belonging to an organization
Leapsome Leapsome API API
The Leapsome API API from Leapsome — 1 operation(s) for leapsome api.
Leapsome payroll API
The payroll API from Leapsome — 2 operation(s) for payroll.
Leapsome reviews API
The reviews API from Leapsome — 4 operation(s) for reviews.
Leapsome Schemas API
Operations on schemas
Leapsome timeTracking API
The timeTracking API from Leapsome — 1 operation(s) for timetracking.
Leapsome users API
The users API from Leapsome — 4 operation(s) for users.
Leapsome workLocations API
The workLocations API from Leapsome — 1 operation(s) for worklocations.
Scroll within the panel for all 14 ·
Open Collections 14
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).
API Collection
OPEN COLLECTIONLeapsome absences API
OPEN COLLECTIONLeapsome absences accessRoles API
OPEN COLLECTIONLeapsome absences auth API
OPEN COLLECTIONLeapsome absences documents API
OPEN COLLECTIONLeapsome absences feedback API
OPEN COLLECTIONLeapsome absences goals API
OPEN COLLECTIONLeapsome absences Groups API
OPEN COLLECTIONLeapsome absences Leapsome API API
OPEN COLLECTIONLeapsome absences payroll API
OPEN COLLECTIONLeapsome absences Schemas API
OPEN COLLECTIONLeapsome absences timeTracking API
OPEN COLLECTIONLeapsome absences users API
OPEN COLLECTIONLeapsome absences workLocations API
OPEN COLLECTIONScroll within the panel for all 14 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Leapsome GraphQL API
Leapsome is a people enablement platform for performance management. The API covers performance reviews, OKRs and goals, learning paths, employee surveys, compensation cycles, a...
GRAPHQLPricing 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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
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.
Leapsome 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.
Leapsome Finops
FINOPSSemantic 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.
Leapsome Context
JSON-LDSpectral Rules 1
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.
Leapsome API Rules
SPECTRALJSON Schema 11
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 SCHEMAEmployee
JSON SCHEMAFeedbackItem
JSON SCHEMAGoal
JSON SCHEMAPayrollCycle
JSON SCHEMASCIM Group
JSON SCHEMASCIM GroupDefinition
JSON SCHEMASCIM User
JSON SCHEMASCIM UserDefinition
JSON SCHEMATimesheet
JSON SCHEMAWorkLocation
JSON SCHEMAScroll within the panel for all 11 ·
Examples 1
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.
Leapsome Api Examples
EXAMPLESecurity Posture 3
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.
Resources
Every other property we hold for Leapsome — 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.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/leapsome · machine-readable index on apis.io
This is an independent, third-party profile of Leapsome, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.