canonical: https://jentic.com/apis/my.15five.com/15five-public-api

# My 15five 15Five Public API

The 15Five Public API reads and creates the performance-management records that 15Five tracks for a company. It lists users and fetches one by id, lists the weekly check-in reports and fetches one, and reads the questions and answers behind them. It lists and creates objectives, fetches a single objective, and lists or posts high-fives, the peer recognition 15Five uses. Every endpoint authenticates with a bearer token.

## For AI agents

Read 15Five performance data: users, weekly check-in reports, questions, and answers, and list, fetch, or create objectives and high-fives.

## Scope

Covers 15Five users, reports, questions, answers, objectives, and high-fives. Does not handle payroll, benefits, or applicant tracking.

## Capabilities

- List users and fetch a single user by id
- List weekly check-in reports and fetch one by id
- Read the questions and the answers behind the reports
- List objectives and fetch a single objective by id
- Create a new objective
- List high-fives and post a new high-five

## Use cases

### Agent Performance Digest

An HR assistant can assemble a read of the team's check-ins without opening 15Five. The agent lists the reports, reads the questions and answers behind them, and summarizes themes, so a manager gets a digest of the week's check-ins grounded in the actual responses rather than a manual skim.

Example prompt: List the week's reports and summarize the questions and answers for a manager

### Objective Sync

A planning agent can keep 15Five objectives aligned with a team's roadmap. It lists the current objectives, compares them with the plan, and creates any that are missing, so goals recorded in 15Five track the roadmap without a person re-entering each one.

Example prompt: List existing objectives and create the ones missing from the team's roadmap

### Recognition Automation

A team-culture agent can post high-fives when it detects a shipped milestone. It reads the existing high-fives to avoid duplicates and posts a new one to recognize a colleague, so peer recognition happens promptly while a person still sets the rule for when it fires.

Example prompt: Read recent high-fives and post a new one to recognize a colleague on a milestone

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/user` | List users |
| GET | `/report` | List weekly check-in reports |
| GET | `/objective` | List objectives |
| POST | `/objective` | Create an objective |
| GET | `/high-five` | List high-fives |
| POST | `/high-five` | Post a high-five |

## Key resources

- **Users** — The account's users, listable and fetchable by id
- **Reports** — Weekly check-in reports, with the questions and answers behind them
- **Objectives** — Objectives that can be listed, fetched by id, and created
- **High-fives** — Peer recognition entries that can be listed and posted

## Why Jentic

- **Setup:** Wiring the 15Five Public API by hand means handling its bearer auth and matching the list-versus-by-id shapes across users, reports, and objectives. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls the users, reports, and objectives operations.
- **Permission scoping:** A rule can allow only the read operations your agent needs, such as users and reports, and leave objective and high-five creation out of scope until you add them. You decide which operations are in scope, and every call the agent makes is logged.
- **Credential handling:** 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.
- **Discovery method:** Agents search Jentic by intent such as 'list 15Five check-in reports' or 'create an objective', and Jentic returns the matching 15Five operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **BambooHR** — HR platform for employee records, time off, and reporting.
- **Gusto** — Payroll, benefits, and HR for small businesses.
- **Lever** — Applicant tracking and recruiting workflows.

## FAQ

### What authentication does the 15Five Public API use?

The 15Five Public API authenticates with a bearer token in the Authorization header, per its OpenAPI spec. When you call it through Jentic, that token is held by your own self-hosted instance and injected at execution time, so it never appears in the agent's prompt or logs.

### Can I read check-in reports and create objectives with the 15Five API?

Yes. Call the reports list endpoint to get the weekly check-ins and read the questions and answers behind them, and use the objectives endpoints to list, fetch, or create objectives. High-fives can be listed and posted the same way.

### What are the rate limits for the 15Five Public API?

The OpenAPI spec for the 15Five Public API does not define rate limits. Check 15Five's developer documentation for the limits tied to your token before running high-volume reads.

### Is there a 15Five API MCP server?

You don't need an MCP server to give your agent the 15Five Public API. Jentic connects it directly from the API Directory: import it, store the bearer token once, and your agent calls the users, reports, and objectives operations without another server's tool definitions loaded into its context.

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

Yes. Write a rule that allows only the read operations you need, such as users and reports, and leave objective and high-five creation out of scope until you add them. The scoped set is yours to choose, and each call the agent makes is recorded.

### How do I read 15Five check-in reports through Jentic?

Search Jentic with an intent like 'list 15Five check-in reports', and it returns the reports list operation with its response schema so the agent calls it and reads back the check-ins. To run it on your own infrastructure, install Jentic One from its GitHub repo.
