canonical: https://jentic.com/apis/layerise.com/layerise # Layerise API Jentic publishes the only available OpenAPI specification for Layerise API, keeping it validated and agent-ready. The Layerise API exposes an employee engagement and recognition platform: agents can read and create user records, give peer recognition, organise people into teams, and read activity feeds that record what each team is doing. The surface is compact, with primary objects for users, recognition events, teams, and activities. It is intended for HR-tech integrations and internal automation rather than complex performance management. ## For AI agents Manage employees, give peer recognition, group people into teams, and read recent activity events on the Layerise engagement platform. ## Scope Does not handle payroll, performance reviews, or rewards redemption - use for employee recognition, teams, and activity feeds only. ## Capabilities - List and create employee user records with role and team metadata - Give peer recognition to a specific user with message and points payload - Read the recognition history for a single user to power an employee profile view - Create and list teams to model organisational structure for recognition workflows - Pull activity feeds to surface recent recognition events in a digest or dashboard ## Use cases ### Peer Recognition From Slack Let employees send recognition without leaving Slack. A bot captures a kudos message and recipient, calls the Layerise recognition endpoint with the giver, recipient, and message, and confirms back in the channel. Removes the context switch into the Layerise UI and increases participation in the recognition program. Example prompt: When a Slack message contains 'kudos to @user for X', POST to /recognition with the recipient userId and the kudos message, then react to the Slack message with a checkmark. ### Team Onboarding Sync Keep Layerise teams aligned with the source-of-truth HRIS or directory. An agent diffs the directory's team list against /teams, creates any missing team via POST /teams, and adds new joiners via POST /users so recognition flows are routed correctly. Removes manual team-management work after every reorganisation. Example prompt: Diff the HRIS team list against GET /teams; for each missing team POST /teams with the name, then POST /users for each new hire with the matching teamId. ### Recognition Digest Email Send a weekly digest summarising recognition across the company. The agent reads /activities for the past seven days, groups events by team, and emails the leadership team a summary of who recognised whom and for what. Surfaces engagement patterns without requiring anyone to log into Layerise. Example prompt: Call GET /activities with a 7-day window, group results by teamId, and email a digest of the top 10 recognitions to managers. ### AI Agent Recognition Coach An AI agent monitors project completions and prompts the team lead to recognise contributors through Jentic. When a deal closes or a release ships, the agent suggests recipients and a message, then calls /recognition once approved. Closes the loop between work happening and recognition being given without manual data entry. Example prompt: Through Jentic, search 'give peer recognition', load the schema for POST /recognition, and execute it with the suggested userId, points, and message after manager approval. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/users` | List users on the platform | | POST | `/users` | Create a new user | | POST | `/recognition` | Give recognition to a user | | GET | `/recognition/{userId}` | Read recognition history for a user | | GET | `/teams` | List teams | | POST | `/teams` | Create a team | | GET | `/activities` | List recent activity events | ## Key resources - **Users** — List, create, and retrieve employee user profiles - **Recognition** — Give recognition to a user and read recognition history - **Teams** — Create and list teams used to group users for recognition flows - **Activities** — Read activity events recording recognition and team actions ## Why Jentic - **Setup:** Wiring the Layerise API by hand means setting the bearer token in the Authorization header, targeting the api.layerise.com host, and mapping the recognition and team endpoints yourself. Through Jentic you install once, import the Layerise API from the API Directory, store the bearer token once, and your agent calls it. - **Permission scoping:** You choose which Layerise operations the agent may call, so you can limit it to the ones it needs, such as posting peer recognition and listing teams. Allowing recognition and read operations lets the agent give recognition without being able to create users or new teams. - **Credential handling:** Your Layerise 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 'give peer recognition' or 'list teams', and Jentic returns the matching Layerise operation with its input schema so the agent calls the right endpoint without parsing the docs. ## Related APIs - **Bonusly API** — Bonusly is a peer-to-peer recognition platform with rewards and points, similar in scope to Layerise. - **Assembly API** — Assembly covers recognition, rewards, and culture workflows across teams. - **BambooHR API** — BambooHR is a core HRIS storing employees, while Layerise records the recognition events on top of those employees. ## FAQ ### Why is there no official OpenAPI spec for Layerise API? Layerise does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Layerise 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 Layerise API use? The Layerise API uses bearer token authentication: each request includes an `Authorization: Bearer ` header. Through Jentic, the bearer token lives in your Jentic One instance and is injected only at execution time. ### Can I send peer recognition through the Layerise API? Yes. POST to /recognition with the recipient userId and the recognition payload. You can then read the recipient's recognition history with GET `/recognition/{userId}` to confirm the entry was recorded. ### What are the rate limits for the Layerise API? Rate limits are not declared in the OpenAPI spec. Treat the API as a moderate-traffic HR integration: batch user and team sync jobs and avoid running recognition writes in tight loops. ### How do I list all employees in a team through Jentic? Run `pip install jentic`, search for 'list layerise users', and execute GET /users with the relevant team filter. To then look at a specific team, call GET `/teams/{teamId}` with the same agent flow. ### Does the Layerise API expose activity feeds? Yes. GET /activities returns the activity feed across the workspace and GET `/activities/{activityId}` returns a single event, which is useful for building recognition digests or audit trails. ### Can I limit what my agent is allowed to do with the Layerise API? Yes. Because you run Jentic One yourself, your own rules decide which Layerise operations and credentials the agent can use, so you can restrict it to only what a task needs. For example, you can allow POST /recognition and read operations like GET /teams and GET /activities so the agent can give peer recognition and read activity, while withholding POST /users and POST /teams so it cannot create new users or teams. The bearer token stays in your own instance and is injected only when an allowed operation runs.