Bonusly API
★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee Managementbearer23 EndpointsREST
For Agents
Send peer-to-peer bonuses, manage employees and redemptions, subscribe to recognition webhooks, and pull recognition analytics through Bonusly.
Use for: I need to send a 50-point bonus to a teammate for shipping a feature, List the top recognised employees this quarter, Deactivate a user who has left the company, Redeem 1000 points for an Amazon gift card on behalf of a user
Not supported: Does not handle payroll, performance reviews, or external customer reviews — use for Bonusly internal recognition, redemptions, and recognition analytics only.
Jentic publishes the only available OpenAPI specification for Bonusly API, keeping it validated and agent-ready. Bonusly is an employee recognition and rewards platform that lets coworkers give each other small bonuses tied to company values. The API exposes 23 endpoints covering bonuses, users, redemptions, achievements, webhooks, and analytics. Use it to send bonuses programmatically, deactivate users when they leave, redeem points for rewards, and pull hashtag trends and leaderboards into HR dashboards.
Install Jentic One Beta
Connect the Bonusly API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bonusly 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Bonusly API.
Send a peer-to-peer bonus from one employee to another with a hashtag and message
Manage the employee roster with create, update, and deactivate operations
Issue a redemption on behalf of a user against the configured rewards catalogue
Subscribe to webhooks to react to new bonuses and redemptions in real time
Pull hashtag trends, leaderboards, and popular words for HR analytics dashboards
List achievements an employee has unlocked through the recognition program
Use Cases
Patterns agents use Bonusly API for, with concrete tasks.
★ Automated Recognition from CI/CD Events
Send a Bonusly bonus automatically when a meaningful event happens — for example, the engineer who closed the most pull requests this sprint, or the support agent with the highest CSAT. POST /v1/bonuses creates the bonus with the giver, receiver, amount, and a hashtag like #craftsmanship. Removes the friction of remembering to recognise in the moment.
POST /v1/bonuses with giver_email lead@example.com, receiver_email engineer@example.com, amount 50, reason '#craftsmanship great PR review'
HRIS-Driven User Lifecycle
Keep the Bonusly user list in sync with the HR system of record. POST /v1/users when someone joins, PUT /v1/users/{id} when their role or manager changes, and DELETE /v1/users/{id} when they leave. Removes the manual offboarding work that often leaves former employees in recognition tools.
DELETE /v1/users/usr_8821 to deactivate the user who left on 2026-06-01
Recognition Analytics Dashboard
Build an internal dashboard that surfaces who is being recognised, around which company values, and which teams are highest engaged. GET /v1/analytics/trends, /v1/analytics/leaderboards, and /v1/analytics/words feed a Looker or internal BI dashboard. Useful for People Ops teams measuring culture programs.
GET /v1/analytics/leaderboards for the last 90 days and write the result to the recognition_leaderboard table
AI Agent People Ops Assistant
An AI agent uses Jentic to discover Bonusly operations, sends bonuses on behalf of managers, and pulls leaderboard data for People Ops reviews. Bonusly bearer credentials live in the Jentic vault so the agent never holds the raw key. Replaces manual recognition admin with a single search-load-execute cycle per action.
Search Jentic for 'send a Bonusly bonus', load the operation, and execute it for the named giver and receiver
Key Endpoints
23 endpoints — jentic publishes the only available openapi specification for bonusly api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/v1/bonuses
Create a bonus
GET
/v1/bonuses
List bonuses
POST
/v1/users
Create a user
DELETE
/v1/users/{id}
Deactivate a user
POST
/v1/users/{id}/redemptions
Create a redemption for a user
POST
/v1/webhooks
Create a webhook
GET
/v1/analytics/leaderboards
Get recognition leaderboards
GET
/v1/analytics/trends
Get hashtag trends
POST
/v1/bonuses
Create a bonus
GET
/v1/bonuses
List bonuses
POST
/v1/users
Create a user
DELETE
/v1/users/{id}
Deactivate a user
POST
/v1/users/{id}/redemptions
Create a redemption for a user
POST
/v1/webhooks
Create a webhook
GET
/v1/analytics/leaderboards
Get recognition leaderboards
GET
/v1/analytics/trends
Get hashtag trends
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Bonusly bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped, short-lived access tokens — the long-lived Bonusly access token never enters the agent context or logs.
Intent-based discovery
Agents search Jentic with intents like 'send a Bonusly bonus' or 'list recognition leaderboards' and Jentic returns the matching operation with its input schema, removing the need to read the Bonusly developer docs.
Time to first call
Direct Bonusly integration: 1-2 days to wire up auth, user provisioning, and webhook handling. Through Jentic: under an hour with search, load, and execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Bonusly API through Jentic.
Why is there no official OpenAPI spec for Bonusly API?
Bonusly does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Bonusly API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Bonusly API use?
Bonusly uses HTTP Bearer authentication — send Authorization: Bearer <token> on every request. Through Jentic the token is held in the encrypted vault and the agent only ever sees a scoped, short-lived bearer.
Can I send a bonus from one user to another with the Bonusly API?
Yes. POST /v1/bonuses with the giver, receiver, amount, and reason (which can include hashtags tied to company values). The bonus appears in both users' feeds and the receiving user's point balance increases.
How do I deactivate a user who has left the company through Jentic?
Search Jentic for 'deactivate a Bonusly user', load the DELETE /v1/users/{id} operation, then execute it with the user's id. The user is removed from active recognition without losing their historical bonuses.
What are the rate limits for the Bonusly API?
The OpenAPI spec does not declare formal rate limits. For high-volume use cases like full HRIS sync, batch user operations rather than firing thousands of /v1/users calls in quick succession.
Can I pull recognition analytics into my BI tool?
Yes. GET /v1/analytics/leaderboards, /v1/analytics/trends, and /v1/analytics/words return aggregated data suitable for a Looker, Mode, or internal BI dashboard. The endpoints accept date range parameters.
GET STARTED