PeopleHR API · unofficial, by Cotlet
Create your own PeopleHR API
PeopleHR: the Integration API is listed on the Core, Pro and Elite+ plans, not on Starter (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your PeopleHR account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in PeopleHR session and returns only what your login can see.
Free 7-day trial, 2,000 credits, no card
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by PeopleHR. PeopleHR is a trademark of its owner. If PeopleHR's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/holiday-requests" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"from": "2026-11-23", "to": "2026-11-27"}' const url = "https://cotlet.dev/api/v1/custom/holiday-requests";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ from: "2026-11-23", to: "2026-11-27" }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/holiday-requests",
headers={"Authorization": f"Bearer {key}"},
json={"from": "2026-11-23", "to": "2026-11-27"},
)
data = res.json()["data"] {
"data": [
{
"employee": "Jamie L.",
"team": "Support",
"from": "2026-11-23",
"to": "2026-11-25",
"status": "requested"
},
{
"employee": "Tom H.",
"team": "Support",
"from": "2026-11-25",
"to": "2026-11-27",
"status": "requested"
}
]
} 01 Build
How do you build a PeopleHR endpoint with Cotlet?
-
Sign in to PeopleHR in your Cloud Browser.
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
-
Do the job once with your agent.
For example: "List the holiday requests waiting for approval next week with the person, team and dates."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a date range or a team, and the fields it returns.
-
Call it with your Cotlet API key.
Each endpoint gets its own address,
POST https://. You send JSON in and get JSON back, from the same signed-in PeopleHR session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for PeopleHR
Cotlet ships no fixed list of PeopleHR endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/holiday-requests Holiday requests waiting
Employee, team, dates and status for each request
-
POST
/api/v1/custom/whos-off Who is off
Holiday and absence for a date range, by team
-
POST
/api/v1/custom/employee-details Employee details
Job title, manager, start date and contact details
-
POST
/api/v1/custom/probation-due Probation reviews due
Employees whose probation ends in a period
-
POST
/api/v1/custom/writesapprove-holiday Approve a holiday request
The request you name, approved, with its new status
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/holiday-requests" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"from": "2026-11-23", "to": "2026-11-27"}' The answer is JSON, with your fields under data:
{
"data": [
{
"employee": "Jamie L.",
"team": "Support",
"from": "2026-11-23",
"to": "2026-11-25",
"status": "requested"
},
{
"employee": "Tom H.",
"team": "Support",
"from": "2026-11-25",
"to": "2026-11-27",
"status": "requested"
}
]
} When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.
03 Uses
What can you use your PeopleHR endpoints for?
- Schedule Cotlet endpoint Slack or email
A Monday holiday list in n8n or Make.
Requests waiting for approval and who is off this week, sent to Slack or email.
- Schedule endpoint calendar
A team calendar.
Who is off, pulled into a shared calendar or a rota sheet.
- Month end endpoint Google Sheets
A headcount sheet.
Starters, leavers and probation dates pulled into Google Sheets for the month.
- Chat agent endpoint holiday and cover
Your own HR assistant.
A chat agent that checks holiday left and team cover before it answers a request.
04 Access
What can an endpoint see and change?
An endpoint works in your own PeopleHR session, so it can read and change only what your PeopleHR login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.
An endpoint that changes something, such as approving a holiday request, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.
05 Official API
Does PeopleHR have an official API?
Access PeopleHR documents an Integration API v4.0 that reads and writes employees, holiday, absence, timesheets and more, with keys an admin makes in Settings > API, and webhooks to a listener URL (checked 20 Nov 2026). Its pricing table lists the API on Core, Pro and Elite+. The full picture with sources: Does PeopleHR have an API or MCP server?
Want ChatGPT or Claude to work in PeopleHR instead of code? See the PeopleHR MCP server.
06 Pricing
What does it cost?
- per successful call
- 10 credits
- when a call fails
- 0
- in the smallest pack
- ≈ 500 calls
- free trial, no card
- 7 days
A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.
PeopleHR API with Cotlet: questions
Is this an official PeopleHR API?
No. Cotlet is independent and not affiliated with PeopleHR. The endpoints you build run in your own signed-in PeopleHR account.
Do I need to code?
Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.
What happens when PeopleHR changes its screens?
An endpoint works while PeopleHR works the way it did when you built it. If PeopleHR changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.
How long can a call take?
Up to 90 seconds, and the answer can be up to 1 MB of JSON.
Build your first PeopleHR endpoint
Sign in once, do the job with your agent and save it as an endpoint.
Try it free nowNo card. Takes about 5 minutes.