Layerise API

Name: Layerise API
Brand: Layerise API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee Managementbearer10 EndpointsREST

For Agents

Manage employees, give peer recognition, group people into teams, and read recent activity events on the Layerise engagement platform.

Install Jentic One Beta

Connect the Layerise API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Layerise 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.

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 | sh

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 instance

Jentic 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 Layerise API.

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

GET STARTED

Start building with Layerise API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Layerise API for, with concrete tasks.

★ 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.

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.

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.

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.

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

10 endpoints — jentic publishes the only available openapi specification for layerise api, keeping it validated and agent-ready.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Layerise bearer tokens are encrypted in the Jentic vault. The agent receives a scoped execution capability rather than the token itself, so the token never appears in prompts, logs, or tool arguments.

Intent-based discovery

An agent searches Jentic with intents like 'give peer recognition' or 'list teams' and Jentic returns the matching Layerise operation with its input schema, so the agent calls the correct endpoint without parsing docs.

Time to first call

Direct Layerise integration: 1-2 days to wire bearer auth, the user/team sync job, and the recognition write path. Through Jentic: under an hour — search, load schema, execute.

FAQs

Specific to using Layerise API through Jentic.

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 at https://app.jentic.com/sign-up.

What authentication does the Layerise API use?

The Layerise API uses bearer token authentication: each request includes an `Authorization: Bearer <token>` header. Through Jentic, the bearer token lives in the Jentic vault 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.

Layerise API

Connect the Layerise API to your agent

Capabilities

Start building with Layerise API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs