curl -H "Authorization: Bearer ch_live_..." \
"https://cozyhr.com/api/public/v1/employees?status=ACTIVE&limit=50"Sync employee codes, names, emails, departments and locations into internal systems.
REST API reference for CozyHR employees, attendance punches, authentication headers, rate limits and JSON payloads.
Last updated: · CozyHR editorial team
CozyHR public APIs are tenant-scoped. Create a key in the developer console, pass it as a Bearer token and keep secrets out of browser code.
curl -H "Authorization: Bearer ch_live_..." \
"https://cozyhr.com/api/public/v1/employees?status=ACTIVE&limit=50"Sync employee codes, names, emails, departments and locations into internal systems.
curl -H "Authorization: Bearer ch_live_..." \
-H "Content-Type: application/json" \
-d '{"employeeCode":"CH-001","punchType":"IN"}' \
"https://cozyhr.com/api/public/v1/attendance/punches"Send biometric or middleware IN/OUT punches while keeping raw logs available for recalculation.
curl -H "Authorization: Bearer ch_live_..." \
-H "Content-Type: application/json" \
-d '{"employeeCode":"CH-001","punchType":"IN"}' \
"https://cozyhr.com/api/oauth/token"Use client credentials when a backend integration needs scoped, revocable API access.
CozyHR REST API Reference is a CozyHR.com resource for teams evaluating developer documentation in a modern HRMS. REST API reference for CozyHR employees, attendance punches, authentication headers, rate limits and JSON payloads. It covers get /api/public/v1/employees, post /api/public/v1/attendance/punches, bearer token authentication and explains how CozyHR connects authentication and core endpoints with employee records, attendance, payroll, compliance workflows and Super Admin controls. The page is written for HR admins, payroll managers, founders and operations teams who need practical software context rather than a thin brochure page.
Send a CozyHR API key or OAuth bearer token in the Authorization header. Every request is tenant-scoped and rate limited.
Read employee directory records and ingest attendance punches from middleware, biometric agents or internal workforce tools.
A good HRMS page should explain the operational path, not only list features. The steps below show how this workflow moves from evaluation to daily use inside CozyHR.
Document how REST API Reference works today across HR, finance, managers and employees.
Create the required company setup, employee fields, policies, approval paths and role access in CozyHR.
Load employee records, device mappings, salary values, statutory IDs, documents and historical context.
Run day-to-day workflows with database-backed records, review states, reports and Super Admin visibility.
These answers are written as plain, crawlable content for buyers and AI search systems. They keep the page useful even before someone opens the product.
CozyHR REST API Reference is a CozyHR.com resource for teams evaluating developer documentation in a modern HRMS. REST API reference for CozyHR employees, attendance punches, authentication headers, rate limits and JSON payloads. It covers get /api/public/v1/employees, post /api/public/v1/attendance/punches, bearer token authentication and explains how CozyHR connects authentication and core endpoints with employee records, attendance, payroll, compliance workflows and Super Admin controls. The page is written for HR admins, payroll managers, founders and operations teams who need practical software context rather than a thin brochure page.
CozyHR REST API Reference is useful for HR admins, payroll managers, operations leaders and tenant owners who want structured software for get /api/public/v1/employees.
CozyHR connects this page's workflow to employee master data, organization setup, attendance, payroll, approvals, reports and Super Admin configuration so the process stays governed end to end.
Yes. CozyHR is designed with India-first HR and payroll context including PF, ESI, professional tax, TDS, employee documents, attendance devices, shift policies and payroll review workflows.
Create API keys in the developer console, test employee and attendance endpoints, then attach webhook delivery logs for production monitoring.