A documented REST API over the same objects the product uses — employees, attendance, payroll outputs, approvals — with scoped keys and rate limits. Push punches from your own devices, pull payroll into your accounting system, or sync people into whatever came first.
Why it exists
An HR platform without an API eventually becomes the system everything else is retyped into. Kuzhu’s REST API exposes the employee record, attendance, leave, payroll outputs and the rest as documented endpoints with token authentication, so your other systems — ERP, custom tools, BI stacks, the intranet — read and write the same truth the UI does.
The API is the product’s own: the same permission model applies, every call is authenticated against API keys you issue and can revoke, and rate limits keep an enthusiastic script from becoming an outage. Webhooks push events — a joiner, an exit, an approved leave — to your endpoints, so integrations react instead of polling.
Typical builds land in days, not quarters: provisioning accounts in other tools when someone joins and cutting them when someone exits; pushing payroll journals into accounting; pulling headcount into the company dashboard; syncing the intranet directory. The documentation is written to be built against, with real request and response examples for every endpoint.
The outcome
“Kuzhu joins your systems instead of becoming another silo.”
Feature by feature
Start
01
REST endpoints over employees, attendance, leave, payroll and more
02
Scoped API keys with least-privilege permissions
03
Webhooks for the events you care about
Outcome
How it works
Most teams have this live inside the first month — the workspace exists on day one, and week three is a parallel run against whatever you use today.
API keys created and revoked from the admin screen, each with its scope, each auditable.
Endpoint documentation with real examples — request, response, errors — for everything exposed.
Read employees and attendance, write what your scope allows, and page through changes since a timestamp.
Webhooks on joiners, exits and approvals push to your endpoints with signed payloads.
Rate limits, per-key audit logs and versioned endpoints keep integrations boring — in the good way.
Worth a closer look
Buyer questions
2 answers
The answer
The highest-value integration in most companies: when HR marks a joiner, the API and webhooks let IT provision email, chat and tool accounts the same hour; a leaver triggers deprovisioning the same day — the security hole of ex-employees with live logins closes structurally. The employee record becomes the identity source of truth it should have been all along.
The answer
The payroll run exposes its journal — component-wise costs by cost centre — which posts into your accounting system through a small scheduled job. Finance stops re-entering salaries as one opaque lump, and the P&L carries the same detail payroll computed, reconciled by construction.
Questions
Something else on your mind? +91 82093 73274 — a person answers, mon–sat, 10am–7pm ist.
Bearer tokens from API keys you issue per integration, each scoped, revocable and individually audited.
Yes — subscribe endpoints to events like joiners, exits and approvals; payloads are signed so you can verify origin.
Yes, generously for real integrations — limits protect the platform and are documented per endpoint class.
Yes — scopes per key, so the dashboard that only reads headcount cannot touch anything else.
Enterprise — along with the integration help to wire your first flows on the call with us.
Works best beside
Other platform modules that share the same employee record, so information moves with the person instead of between spreadsheets.
No polished slides. No imaginary employee data. Walk us through how your HR actually works today and see where Kuzhu can take the work off your team.
30 minutes · Your numbers · Your questions
What happens in the demo
Attendance, payroll, approvals — whatever is creating the most work.
You see exactly how the workflows connect instead of hearing a feature list.
If Kuzhu is not the right answer, we will tell you.
Ready when you are.
Kuzhu HRMS
