Roles & Permissions
Granular, per-organization RBAC - assign exactly the right access to every role, out of the box or custom.
Read more All features
API Access
Create API keys so your own systems can read employees, attendance, and leave over a REST API.
Overview
API Access lets your own systems connect to EvoqHR securely. Create an API key, give it only the access it needs, and read employee, attendance, and leave data over a REST API.
Keys are managed by your administrators, can be revoked at any time, and are rate-limited. The feature is optional and enabled by an administrator.
How it works - step by step
- 1An administrator enables API access.
- 2Create a key and choose its scopes.
- 3Copy the key - it is shown only once.
- 4Your system calls the API with the key.
- 5Review API logs to see usage.
- 6Revoke a key immediately if it is no longer needed.
Key capabilities
- Create and revoke API keys from the portal.
- Scopes that limit what each key can read.
- Read employees, attendance, and leave over REST.
- Rate limiting per key.
- API logs showing how keys are used.
- Keys are shown once and stored securely.
Benefits
- Connect HR data to your own tools.
- Least-privilege keys.
- Visibility with API logs.
- No need to share logins.
Who gets what
- Developers: a simple REST API for reading HR data.
- Admins: control over keys, scopes, and logs.
- Security teams: least-privilege access and auditability.
What it replaces
- Manual exports to feed other systems.
- Shared accounts used by scripts.
- Copy-pasting data between tools.
Common questions
Can the API change data?
The API is for reading employees, attendance, and leave data, with scopes that limit what each key can read.
What happens if a key leaks?
Revoke it from the portal and create a new one; revoked keys stop working immediately.
See API Access in action
Create a separate key per integration with only the scopes it needs - it makes revoking one safe and simple.
You may also like
More to read, picked for the topics on this page.