15Five Public API
★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee Managementbearer11 EndpointsREST
For Agents
Read 15Five performance data and create objectives or recognition entries so an agent can keep goals, check-ins, and team feedback in sync with other HR systems.
Use for: I need to create a new objective for an employee in 15Five, Get the latest check-in answers for a direct report, Post a High Five recognising a teammate's work, List all users in the 15Five workspace
Not supported: Does not handle payroll, benefits, time tracking, or applicant tracking - use for 15Five performance management data only.
Jentic publishes the only available OpenAPI specification for 15Five Public API, keeping it validated and agent-ready. 15Five is a continuous performance management platform that helps managers and employees track objectives, run weekly check-ins, gather feedback through reviews, and recognise teammates with High Fives. The Public API exposes 11 read and write operations across users, objectives, high fives, questions, answers, and reports so that performance data can be pulled into other HR systems or surfaced to AI agents. It is a focused performance-management surface rather than a full HRIS, designed for syncing engagement and goal-setting data with downstream tools.
Install Jentic One Beta
Connect the 15Five Public API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 15Five Public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2F15five.com%2F15five" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2F15five.com%2F15five" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with 15Five Public API.
Retrieve user profiles and roster data from 15Five for syncing with HRIS systems
Create and read OKR-style objectives so agents can roll up goal progress across teams
Send peer recognition by posting High Fives on behalf of employees
Pull check-in answers and the questions they were asked to summarise weekly status
Fetch performance reports for managers preparing 1:1s or quarterly reviews
Look up an individual employee record by user ID for downstream enrichment
Use Cases
Patterns agents use 15Five Public API for, with concrete tasks.
★ Sync Performance Data Into a Central HR Warehouse
People-ops teams running 15Five alongside other HR tools often need a unified view of objectives, check-ins, and recognition events. The 15Five Public API exposes read endpoints for users, objectives, answers, questions, high fives, and reports so an ETL job can pull performance signals on a schedule and load them into a warehouse for analytics. Authentication is bearer-token based and the surface is small enough to map cleanly to a star schema in a few hours.
Fetch all users via /user, then for each user retrieve their objectives via /objective and load the combined dataset into a destination table
Automate Peer Recognition From Chat or Workflow Tools
Teams that want to drive engagement often wire recognition into the tools where work happens - Slack shoutouts, retro boards, or sales-win automations. POST /high-five lets an automation create a recognition entry in 15Five whenever a trigger fires elsewhere, so every public thank-you is also captured in the performance record. Reads on /high-five let downstream dashboards aggregate recognition trends by team or manager.
Call POST /high-five with the recipient user ID and message to record a recognition event, then verify the entry exists by listing recent high fives
Manager Briefing Bot for 1:1s and Reviews
Before a manager meets with a direct report, they need a quick snapshot of objectives in flight, the most recent check-in answers, and any standing questions. The Public API surface - /objective, /question, /answer, and /report - gives an agent everything it needs to generate that briefing without the manager opening 15Five. The API is read-mostly for these resources, so the agent can pre-compute summaries on a cadence.
For a given user ID, fetch their objectives, latest answers, and most recent report, then synthesise a one-page briefing with open goals and recent feedback themes
AI Agent Performance Operations Through Jentic
An AI agent connected to Jentic can drive 15Five performance workflows alongside other HR tools without bespoke integrations. With 15Five operations indexed in Jentic, the agent searches by intent - for example creating an objective or fetching a report - and Jentic returns the right operation with input schema. Bearer credentials stay in your Jentic One instance, so the agent never sees the raw token.
Search Jentic for 'create a 15Five objective', load the schema for POST /objective, then execute it with a title, owner user ID, and target date
Key Endpoints
11 endpoints — jentic publishes the only available openapi specification for 15five public api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/user
List all users in the workspace
GET
/user/{userId}
Retrieve a single user by ID
GET
/objective
List objectives
POST
/objective
Create a new objective
GET
/objective/{objectiveId}
Retrieve an objective by ID
POST
/high-five
Post a peer recognition entry
GET
/answer
List check-in answers
GET
/report/{reportId}
Retrieve a single performance report by ID
GET
/user
List all users in the workspace
GET
/user/{userId}
Retrieve a single user by ID
GET
/objective
List objectives
POST
/objective
Create a new objective
GET
/objective/{objectiveId}
Retrieve an objective by ID
POST
/high-five
Post a peer recognition entry
GET
/answer
List check-in answers
GET
/report/{reportId}
Retrieve a single performance report by ID
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the 15Five Public API by hand means managing its bearer token, targeting the my.15five.com public base, and shaping objective and check-in payloads yourself. Through Jentic you install once, import the 15Five Public API from the API Directory, store the token once, and your agent calls it.
Permission scoping
15Five puts the user, objective, and report id in the URL path (/user/{userId}, /objective/{objectiveId}), so a rule can pin your agent to a specific resource such as one objective. You choose the operations it may call, so writes like creating an objective or posting a high-five are not included unless you add them.
Credential isolation
Your 15Five bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a 15Five objective' or 'get check-in answers for a user', and Jentic returns the matching 15Five operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using 15Five Public API through Jentic.
Why is there no official OpenAPI spec for 15Five Public API?
15Five does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call 15Five Public 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 15Five Public API use?
The API uses HTTP bearer authentication. Every request must include an Authorization header in the form Authorization: Bearer <token>, where the token is generated from a 15Five admin account. When you call 15Five through Jentic, the bearer token is held in your Jentic One instance and the agent receives a scoped execution context rather than the raw token.
Can I create objectives programmatically with the 15Five Public API?
Yes. POST /objective creates a new objective and GET /objective lists existing ones, with GET /objective/{objectiveId} for a single record. This makes it possible to provision OKRs from a planning tool or roll quarterly goals down from a parent system without manual entry in 15Five.
How do I send a High Five to recognise a teammate through the API?
Call POST /high-five with the recipient and message in the request body. Reading existing recognition is done with GET /high-five. This is useful for piping shoutouts from chat tools - when a recognition message is detected upstream, the agent posts the high five so it lands in the employee's performance record.
What are the rate limits for the 15Five Public API?
15Five does not publish rate limits in the OpenAPI spec, so production integrations should implement exponential backoff on HTTP 429 responses and cache read-heavy resources such as /user and /question where possible. If you hit limits, reduce concurrency on bulk syncs and stagger jobs across off-peak windows.
How do I summarise check-in data for a manager through Jentic?
Run pip install jentic, then search Jentic for an intent like 'get 15Five check-in answers for a user', load the schema for GET /answer (and GET /question for the prompts), and execute against the target user ID. The agent gets back the answer payload it can summarise without ever holding the bearer token directly.
Can I limit what my agent is allowed to do with the 15Five Public API?
Yes. Jentic One is self-hosted, so you set the rules that decide which 15Five operations your agent may call and which credentials it may use. Because 15Five puts the resource id in the URL path, such as /user/{userId} and /objective/{objectiveId}, you can pin the agent to a specific record like a single objective. You also choose the operations it can reach, so write actions such as POST /objective or POST /high-five stay excluded until you explicitly allow them.
GET STARTED