PeopleForce Open API and webhooks for custom integrations

Ways to connect

How do you want to connect it?

Most connections need no developers at all. Start at the level that matches your team.

No developers: a ready app in Zapier

Our official Zapier app ships 13 triggers and 3 actions — hiring, terminations, position and salary changes, leave requests, accepted offers. Connect it with a company API key and pick the app on the other side.

Low code: your own automation tool

n8n, Make or anything that speaks HTTP works with the same API key and the same webhooks. Teams already run referral intake, overtime adjustments and onboarding tickets this way.

Your engineers: an integration you build

A documented REST API that reads and writes your people, org structure, compensation, time off, time tracking and recruiting data, with published OpenAPI specifications. Build a dashboard, a portal or an assistant on top of it.

Data you can access

Which data can you read and write?

PeopleForce stays the source of truth for people data. Everything below can be pulled into your systems, written back, or both.

Object	Read	Write	Webhook events
People and profiles	Yes	Yes	Hired, updated, first day, terminated
Org structure	Yes	Yes	Position and job profile changes
Compensation	Yes	Yes	Salary and additional pay changes
Time off	Yes	Yes	Created, approved, rejected, withdrawn, deleted
Overtime	Yes	Yes	Created, updated, approved, deleted
Time tracking	Yes	Yes	—
Recruiting	Yes	Yes	Candidate, vacancy, application, pipeline move, offer
Performance	Yes	KPI only	—
Surveys	v4 only	—	Survey launched

Salary and compensation data needs its own permission on the key. Survey data is read through the newer v4 API, which uses a service account key rather than the company key.

Full endpoint reference and field-level detail

They live in the developer documentation

Developer docs

Events

What happens the moment data changes?

Instead of polling us on a schedule, subscribe to 36 events and let PeopleForce tell your systems when something happened.

Signed deliveries

Delivered to your HTTPS endpoint. Set a secret on it and every delivery is signed with HMAC‑SHA256, so you can verify it came from us.

A log for every delivery

Every delivery is logged with its request and response, and can be sent again from the settings screen.

Set up in the interface or through the API

Endpoints are set up in the interface, and can also be created or removed through the API.

Group	Events
People	Created, updated, first day, terminated, termination cancelled
Compensation	Salary changed, additional pay added or changed, employment status changed
Time off	Created, approved, rejected, withdrawn, deleted
Overtime	Created, updated, approved, deleted
Recruiting	Candidate created or deleted, vacancy created, application created, pipeline move, offer accepted or rejected
Structure and access	Positions, job profiles, custom table rows, external users, survey launched

How it works

How it works end to end

One new hire, four steps, no one retyping anything.

1. A new hire is added

HR fills the profile in PeopleForce, as they already do today.

2. PeopleForce sends the event

Your endpoint receives a signed webhook with the person and their start date.

3. Your systems act on it

Accounts are created, a ticket opens for the laptop, access is granted.

4. The result comes back

Your workflow writes the account details back into the profile through the API.

Where to start

The key belongs to the company, so nothing depends on one person staying with you.

1. Create an API key

Settings → API keys, open to any role you give that setting to. The key is shown once and belongs to the company, not to the person who made it.

2. Call your first endpoint

Send the key in the request header and read your people, departments or vacancies.

3. Subscribe to the events you care about

An administrator adds a webhook endpoint, picks its topics and checks the delivery log.

Currently 300 requests a minute, per key	Enough to pull a few thousand people on a nightly sync. Go over it and the response tells you how long to wait before retrying.
Each key can be locked to your own addresses	Add an IP allowlist to a key and it stops working from anywhere but your servers.
The specification is published	Generate a client in your own language instead of writing every request by hand.
Older versions stay available	Versions one to three share the same paths, so an integration written against an earlier one keeps running. Version four is a separate, newer API you move to when you need what it adds.