PeopleHR API

Name: PeopleHR API
Brand: PeopleHR API
Availability: InStock

✓ Official Vendor SpecProductivityTask ManagementapiKey116 EndpointsREST

For Agents

Manage peoplehr.com resources and operations programmatically.

Use for: I need to integrate with peoplehr.com, How do I access peoplehr.com data programmatically, Help me automate peoplehr.com tasks

Not supported: Provides access to peoplehr.com resources and operations as documented in the OpenAPI specification.

PeopleHR API for HR administration. All API calls need the API key to be passed along with the JSON data sent as part of the HTTP request. Rate limit: 30 calls per minute per IP address.

Install Jentic One Beta

Connect the PeopleHR API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PeopleHR 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpeoplehr.com%2Fpeoplehr" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpeoplehr.com%2Fpeoplehr" | 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 PeopleHR API.

Access and manage peoplehr.com resources

Integrate peoplehr.com functionality into workflows

Automate peoplehr.com operations

Use Cases

GET STARTED

Start building with PeopleHR API

Explore with Jentic One

View OpenAPI Document

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring PeopleHR by hand means setting the APIKey header on every request and working through its action-style Employee, EmployeeSalary, and EmployeeHoliday endpoints yourself. Through Jentic you install once, import the PeopleHR API from the API Directory, store the key once, and your agent calls it.

Permission scoping

PeopleHR exposes action-style operations such as GetEmployeeDetailById, CreateNewEmployee, and MarkAsLeaverById rather than resource ids in the URL path, so scoping is operations-only: limit the agent to the operations it needs, such as reading employee detail, and leave destructive ones like marking a leaver out of the allowed set unless you add them.

Credential isolation

Your PeopleHR API key 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.

Intent-based discovery

Agents search Jentic by intent such as 'get an employee's details', and Jentic returns the matching PeopleHR operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using PeopleHR API through Jentic.

What authentication does the PeopleHR API use?

The PeopleHR API uses apiKey authentication. Through Jentic, credentials are stored encrypted and injected at execution time so they never enter the agent's context.

How many endpoints does the PeopleHR API have?

The PeopleHR API exposes 116 endpoints across its surface area.

Can I limit what my agent is allowed to do with the PeopleHR API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which PeopleHR operations your agent may call and which credentials it uses. Since PeopleHR uses action-style operations rather than resource ids in the path, you scope at the operation level: allow only what the agent needs, such as GetEmployeeDetailById to read employee detail, while keeping destructive actions like CreateNewEmployee and MarkAsLeaverById out of the allowed set. The stored API key is injected only for the operations you have permitted, so anything you leave out of the set cannot be called.