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