Factorialhr Factorial API

Name: Factorial API
Brand: Factorial API
Availability: InStock

✓ Official Vendor SpecHR recruitingEmployee Managementoauth225 EndpointsREST

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.

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.

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the Factorial API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Factorial API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffactorialhr.com%2Ffactorial" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffactorialhr.com%2Ffactorial" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Factorial 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

Start building with Factorial API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Factorial 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.

Key Endpoints

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

GET

/employees/employees

List all employees

POST

/employees/employees

Create a new employee

POST

/attendance/shifts/clock-in

Clock an employee in

POST

/attendance/shifts/clock-out

Clock an employee out

POST

/timeoff/leaves

Submit a time-off leave request

GET

/ats/applications

List ATS applications

GET

/employees/employees

List all employees

POST

/employees/employees

Create a new employee

POST

/attendance/shifts/clock-in

Clock an employee in

POST

/attendance/shifts/clock-out

Clock an employee out

POST

/timeoff/leaves

Submit a time-off leave request

GET

/ats/applications

List ATS applications

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Factorial API by hand means running its OAuth 2.0 flow, rotating refresh tokens, targeting the dated api.factorialhr.com resources base, and coordinating employees, attendance, and ATS routes yourself. Through Jentic you install once, import the Factorial API from the API Directory, store the OAuth credential once, and your agent calls it.

Permission scoping

Factorial's core routes here act on collections with the record details in the request body, so you limit the agent to the operations it needs, such as listing employees, clocking a shift in or out, or submitting a time-off request. You choose those operations, so employee creation or ATS reads are not included unless you add them.

Credential isolation

Your Factorial OAuth 2.0 credential and refresh token are stored once, encrypted, by your own Jentic One instance and a scoped token is injected at execution time. The client_id, client_secret, and bearer tokens never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'submit a time-off request' or 'clock an employee in', and Jentic returns the matching Factorial operation with its input schema so the agent calls the right endpoint without browsing the developer docs.

FAQs

Specific to using Factorial 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.

Can I limit what my agent is allowed to do with the Factorial API?

Yes. Because you run Jentic One yourself, you decide which Factorial operations your agent may call, so you can grant only what a given workflow needs, such as listing employees, clocking a shift in or out, or submitting a time-off request. Higher-impact routes like creating an employee record or reading the ATS application pipeline stay out of reach unless you explicitly add them. Your OAuth credential is held by your own instance and a scoped token is injected only at execution time, so the agent never handles the raw client secret or bearer token.

Factorialhr Factorial API

Connect the Factorial API to your agent

Capabilities

Start building with Factorial API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs