For Agents
Manage employees, attendance shifts, time off requests, applications, and HR webhooks across a Factorial workspace. Useful for onboarding, time tracking, and payroll preparation flows.
Get started with Factorial API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"create a Factorial employee"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Factorial API API.
Create and update employee records on the workspace
Clock employees in and out and read attendance shift history
Submit and approve time-off leave requests
Track applicants through the ATS application pipeline
Subscribe to webhooks that notify on employee, attendance, and time-off changes
GET STARTED
Use for: I need to add a new employee to Factorial, Clock an employee in for the start of their shift, Submit a time-off request for an employee, List all open applications in the ATS
Not supported: Does not handle payroll execution, benefits enrollment, or accounting ledgers — use for HRIS records, attendance, time off, and ATS only.
Factorial is an HR management platform whose API exposes employee records, attendance shifts, time off, applicant tracking, finance, tasks, and webhook subscriptions across 25 endpoints. The API is dated by version (2026-01-01) and is grouped by tag for ATS, Attendance, Employees, Finance, System, Tasks, Time Off, and Webhooks. It is a single integration point for people-ops automations rather than a narrow point solution.
Read finance data attached to employees and contracts
Assign and complete tasks linked to HR workflows
Patterns agents use Factorial API API for, with concrete tasks.
★ New Hire Onboarding
When a candidate is hired through the Factorial ATS, an automation creates the employee record, opens the relevant attendance schedule, and registers a webhook so payroll and IT systems are notified on employee changes. The flow uses POST /employees/employees, the attendance shifts endpoints, and the Webhooks subscription tag. Typical setup runs in minutes once the ATS hand-off is wired.
POST the candidate payload to /employees/employees, register a webhook on the Webhooks tag for employee.created events, and confirm the new employee id is returned.
Daily Attendance Sync
An attendance integration reads each employee's clock-in and clock-out events at end of day, reconciles them against a scheduling system, and pushes corrections back. The flow centres on /attendance/shifts with POST /attendance/shifts/clock-in and POST /attendance/shifts/clock-out for write paths. Designed for daily batch runs over a workforce of hundreds of employees.
List shifts via GET /attendance/shifts for the day, post any missing clock-in entries via POST /attendance/shifts/clock-in, and reconcile clock-out times against the scheduling system.
Time-Off Request Workflow
An employee submits a leave request through a chat interface; the agent posts the request to Factorial, listens for the approval webhook, and updates the requester. The flow uses POST /timeoff/leaves to create the request and a Webhooks subscription to react to the approval state change. Suitable for self-service time-off bots running over Slack or Teams.
POST the leave details to /timeoff/leaves, register a webhook for leave approval events, and message the employee when the approval status changes.
Applicant Tracking Pipeline
A recruiting agent lists open applications in the ATS, filters by stage, and posts updates as candidates move through interviews. The /ats/applications endpoint exposes the application list and downstream operations under the ATS tag handle stage transitions. Suited to recruiters who want a chat agent to summarise pipeline state on demand.
Call GET /ats/applications, group results by stage, and return a summary of candidates in each stage with the most recent update.
AI Agent People-Ops Assistant
An AI agent embedded in a people-ops workflow uses Jentic to discover Factorial operations and answer questions like 'who is on leave next week' or 'create an employee record for this hire'. Jentic exposes the 25 Factorial operations with their schemas, so the agent does not need to read the developer docs. Designed for HR teams running an internal assistant over Slack.
Call jentic.search with 'list employees on leave next week', load the /timeoff/leaves operation, execute with a date-range filter, and return the resulting employee names.
25 endpoints — factorial is an hr management platform whose api exposes employee records, attendance shifts, time off, applicant tracking, finance, tasks, and webhook subscriptions across 25 endpoints.
METHOD
PATH
DESCRIPTION
/employees/employees
List all employees
/employees/employees
Create a new employee
/attendance/shifts/clock-in
Clock an employee in
/attendance/shifts/clock-out
Clock an employee out
/timeoff/leaves
Submit a time-off leave request
/ats/applications
List ATS applications
/employees/employees
List all employees
/employees/employees
Create a new employee
/attendance/shifts/clock-in
Clock an employee in
/attendance/shifts/clock-out
Clock an employee out
/timeoff/leaves
Submit a time-off leave request
Three things that make agents converge on Jentic-routed access.
Credential isolation
Factorial OAuth 2.0 client credentials and refresh tokens are stored in the Jentic vault and rotated by the platform. Agents receive a scoped execution permission so client_id, client_secret, and bearer tokens never appear in the agent's context.
Intent-based discovery
Agents search Jentic by intent (e.g. 'submit a time-off request' or 'clock employee in') and Jentic returns the matching Factorial operations with their input schemas, so the agent can call the right endpoint without browsing developer docs.
Time to first call
Direct Factorial integration: 2-4 days for OAuth, webhook handling, and pagination. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
BambooHR
US-focused HRIS with employee, time-off, and applicant tracking
Choose BambooHR when the workspace is centred on US payroll providers and Bamboo's onboarding workflows are already in use.
Personio
European HRIS covering employees, attendance, and recruiting
Choose Personio for German-speaking markets where Personio is the incumbent HRIS rather than Factorial.
Greenhouse
Dedicated ATS with deeper recruiting workflows
Use Greenhouse for the recruiting pipeline and Factorial for the post-hire HRIS record once a candidate is hired.
Workable
ATS that often feeds candidate data into HRIS systems
Use Workable to source and screen candidates and Factorial to materialise the employee record after offer acceptance.
Specific to using Factorial API API through Jentic.
What authentication does the Factorial API use?
Factorial uses OAuth 2.0 with the authorization code flow — authorization at https://api.factorialhr.com/oauth/authorize and token exchange at https://api.factorialhr.com/oauth/token. Through Jentic, the OAuth client and refresh tokens are held in the vault and rotated automatically, so the agent only sees a scoped execution permission.
Can I create an employee record with the Factorial API?
Yes. POST the new hire payload to /employees/employees. The endpoint returns the created employee id which is used to attach attendance, time-off, and finance records on subsequent calls.
What are the rate limits for the Factorial API?
Rate limits are not declared in the spec. Factorial enforces fair-use throttling on the production tenant — keep batch operations sequential for large workspaces and inspect 429 responses for retry-after hints.
How do I clock an employee in through Jentic?
Run pip install jentic, call jentic.search with 'clock employee in', and execute the returned /attendance/shifts/clock-in operation with the employee id and timestamp. Jentic handles the OAuth token exchange so no client credentials enter the agent context.
Does the Factorial API support webhooks?
Yes. The Webhooks tag exposes operations to subscribe to events including employee changes, attendance updates, and time-off approvals. Use these to drive downstream payroll and IT provisioning flows rather than polling the resource endpoints.
How do I list ATS applications?
Call GET /ats/applications. The response lists applications across the recruiting pipeline; downstream operations under the ATS tag move candidates between stages or attach notes to an application.
/ats/applications
List ATS applications