canonical: https://jentic.com/apis/leapsome.com/leapsome

# Leapsome API

Jentic publishes the only available OpenAPI specification for Leapsome API, keeping it validated and agent-ready. The Leapsome API exposes core read access to a performance management and employee development platform: agents can list employees, retrieve performance reviews, and read goal records. The surface is intentionally small and read-only, focused on syncing review and goal data into reporting tools or AI agents rather than authoring new content.

## For AI agents

Read employees, performance reviews, and goal records from Leapsome to feed BI dashboards, talent reviews, and agent-driven reporting workflows.

## Scope

Does not handle payroll, recruiting, or write operations on reviews and goals - use for read-only employee, review, and goal access only.

## Capabilities

- List employees on the Leapsome platform with role and department metadata
- Retrieve completed and in-progress performance review records for analytics
- Read goal records to track OKRs and individual objectives across the company
- Sync review and goal data into a warehouse for cross-system people analytics
- Power AI agents that summarise an employee's recent reviews and goals on demand

## Use cases

### People Analytics Warehouse Sync

Centralise Leapsome data in a BI warehouse for cross-system people analytics. The agent calls /users for the employee list, /reviews for performance review records, and /goals for active objectives, then loads each result set into a warehouse table. Replaces brittle CSV exports and keeps the analytics layer current without manual reruns.

Example prompt: Call GET /users, /reviews, and /goals; load each response into the matching warehouse table and emit a summary of the row counts.

### Manager Talent Review Brief

Generate a one-pager for a manager preparing a calibration session. The agent pulls the manager's direct reports from /users, fetches their recent reviews from /reviews, reads current goals from /goals, and renders a summary card per report. Removes hours of manual cross-referencing across the Leapsome UI.

Example prompt: Filter /users by managerId, then for each report join /reviews and /goals on userId and render a one-page summary.

### Goal Progress Slack Reminder

Nudge employees about goals due this quarter. The agent reads /goals filtered to the current quarter, joins each goal to its owner via /users, and posts a personalised Slack reminder to anyone whose goals are still open. Lifts goal completion without managers having to chase manually.

Example prompt: Read /goals where due date is within the current quarter and status != 'completed', then DM each owner via Slack with the goal title and due date.

### AI Agent Performance Summary via Jentic

An AI agent built on Jentic answers manager questions like 'show me how Alex has performed this year'. The agent searches Jentic for the matching Leapsome operation, reads the user, joins reviews and goals, and produces a narrative summary backed by the underlying records.

Example prompt: Through Jentic, search 'list leapsome reviews', execute /reviews filtered by userId, and combine with /goals to produce a year-to-date performance narrative.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /users | List employees on the platform |
| GET | /reviews | List performance review records |
| GET | /goals | List goals and OKRs |

## Key resources

- **Users** — List employees with department and role metadata
- **Reviews** — Performance review records with cycle and rating fields
- **Goals** — Goal and OKR records with owner, due date, and status

## Why Jentic

- **Setup:** Wiring the Leapsome API by hand means setting the API key in the Authorization header, targeting the api.leapsome.com host, and mapping the user, review, and goal endpoints yourself. Through Jentic you install once, import the Leapsome API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Leapsome API is read-only, and you choose which operations the agent may call, so you can limit it to the ones it needs, such as listing users, reviews, and goals. Every allowed operation is a read, so the agent cannot change review or goal data.
- **Credential handling:** Your Leapsome API key is stored once, encrypted, by your own Jentic One instance and applied to the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list Leapsome reviews' or 'get employee goals', and Jentic returns the matching Leapsome operation with its input schema so the agent calls the right endpoint without reading the docs.

## Related APIs

- **BambooHR API** — BambooHR is the HRIS source of truth for employees; Leapsome adds performance and goals on top.
- **Workday API** — Workday includes performance management as part of a full HCM suite, while Leapsome is a focused performance and development platform.
- **Gusto API** — Gusto runs payroll and benefits while Leapsome runs reviews and goals - pairing them gives a fuller employee view.

## FAQ

### Why is there no official OpenAPI spec for Leapsome API?

Leapsome does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Leapsome API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Leapsome API use?

The Leapsome API uses an API key passed in the `Authorization` header. Through Jentic, the key sits encrypted in the credential vault and is added to the header at execution time, so it never appears in the agent's prompt or logs.

### Can I read performance reviews from the Leapsome API?

Yes. GET /reviews returns review records with cycle, reviewer, and rating fields. The endpoint is read-only - review authoring still happens inside Leapsome's UI.

### What are the rate limits for the Leapsome API?

The OpenAPI spec does not declare rate limits. Treat the API as a moderate-volume HR integration: warehouse-sync flows should run on a schedule with backoff rather than continuous polling.

### How do I list goals through Jentic?

Run `pip install jentic`, search 'list leapsome goals', and execute GET /goals. The Jentic flow returns the goal records ready to filter by quarter or owner without manually constructing the request.

### Does the Leapsome API let me create or update reviews and goals?

Not in this version of the spec. The exposed endpoints are read-only - GET /users, GET /reviews, and GET /goals. Use the Leapsome UI or contact Leapsome directly for write access.

### Can I limit what my agent is allowed to do with the Leapsome API?

Yes. Because you run Jentic One yourself, your own rules decide which Leapsome operations the agent may call and which credentials it may use. The Leapsome API is read-only, so you can allow just the operations an agent needs, such as GET /users, GET /reviews, and GET /goals, and withhold the rest. Since every permitted operation is a read, the agent can pull employee, review, and goal data but cannot change any review or goal records.