Factorial HR API

Name: Factorial HR API API
Brand: Factorial HR API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee Managementbearer30 EndpointsREST

For Agents

Manage Factorial HR employees, teams, time-off requests, attendance shifts, payroll supplements, and HR documents through a versioned API.

Connect the Factorial HR API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Factorial HR 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 HR API API.

List, create, update, and delete employee records under /resources/core/employees

Manage teams and their membership through /resources/core/teams

Submit and approve time-off leave requests via /resources/time_off/leaves

Record and update attendance shifts via /resources/attendance/shifts

GET STARTED

Start building with Factorial HR API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Factorial HR API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Factorial HR API, keeping it validated and agent-ready. Factorial is a European HR platform used by SMEs to manage employees, teams, time off, attendance shifts, payroll supplements, and HR documents. The 2024-10-01 API surface gives programmatic access to the core HR record (employees, teams), the request flows for time off and attendance, and document storage, so integrators can sync HR data into IT, finance, or recruitment workflows. Authentication uses a bearer token issued from the Factorial workspace settings.

Use Cases

Patterns agents use Factorial HR API API for, with concrete tasks.

★ HRIS Synchronisation

Engineering and IT teams sync Factorial employees into Okta, Jira, and Slack so that joiners get the right access on day one and leavers are deprovisioned automatically. GET /resources/core/employees lists the workforce and the team endpoints expose reporting structure, so a downstream IAM platform can mirror the HR record without manual exports.

List employees via GET /resources/core/employees, diff against the IAM directory, and create or deprovision accounts based on the result.

Time-off Request Automation

Operations teams replace email-based holiday requests with a Slack or Microsoft Teams flow that creates a leave directly in Factorial. POST /resources/time_off/leaves submits the request and GET /resources/time_off/leaves/{id} polls for approval, while GET /resources/time_off/policies surfaces the available leave types so the form stays in sync with HR policy.

Create a leave request via POST /resources/time_off/leaves with the employee ID, start date, end date, and policy, then notify the manager.

Payroll Supplement Feed

Finance teams running monthly bonuses, commissions, or expense reimbursements push them into Factorial as payroll supplements rather than emailing spreadsheets. POST /resources/payroll/supplements adds the line item against an employee and GET /resources/payroll/supplements lists what is queued for the next payroll run, giving finance an auditable trail.

Create payroll supplements for the sales team's monthly commission via POST /resources/payroll/supplements with the employee ID, amount, and label.

AI Agent HR Assistant

An AI agent acting as an HR copilot can use Jentic to answer 'who is on leave next week' or 'create a leave request for me' without managing the Factorial bearer token directly. Jentic returns the matching operation by intent search, validates inputs against the schema, and isolates credentials so the agent never sees the raw token.

Search Jentic for 'submit a time-off request', load the POST /resources/time_off/leaves schema, and execute it using the requesting employee's ID and date range.

Key Endpoints

30 endpoints — jentic publishes the only available openapi specification for factorial hr api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/resources/core/me

Get the current authenticated user.

GET

/resources/core/employees

List employees in the workspace.

POST

/resources/core/employees

Create a new employee record.

POST

/resources/time_off/leaves

Submit a time-off leave request.

GET

/resources/time_off/policies

List the configured time-off policies.

POST

/resources/attendance/shifts

Record an attendance shift for an employee.

POST

/resources/payroll/supplements

Add a payroll supplement to the next payroll run.

GET

/resources/documents/documents

List HR documents.

GET

/resources/core/me

Get the current authenticated user.

GET

/resources/core/employees

List employees in the workspace.

POST

/resources/core/employees

Create a new employee record.

POST

/resources/time_off/leaves

Submit a time-off leave request.

GET

/resources/time_off/policies

List the configured time-off policies.

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Factorial bearer tokens are stored in the encrypted Jentic vault (MAXsystem). Agents receive scoped access tokens — the raw token never enters the agent's prompt or tool output.

Intent-based discovery

Agents search Jentic by intent (e.g., 'submit a time-off request') and receive the matching Factorial operation with its full input schema, so the agent can fill the right fields without reading the Factorial docs site.

Time to first call

Direct Factorial integration: 1-2 days reading the HTML reference, building auth, and handling 429 backoff. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

BambooHR API

US-focused HRIS covering employees, time off, and reports — same shape, different geography.

Choose BambooHR for US-headquartered customers; Factorial is the more common choice in Europe.

Alternative

Gusto API

US payroll-first HR platform that complements employee records with full payroll execution.

Choose Gusto when payroll execution itself needs to be triggered via API; Factorial only exposes payroll supplements.

Alternative

Rippling API

Unified HR + IT + finance platform with deeper IT provisioning than Factorial.

Choose Rippling when the workflow also needs device management and SaaS provisioning, not just HR records.

Alternative

HiBob API

European-friendly HRIS with rich people analytics and similar API coverage.

Choose HiBob when the customer prioritises people analytics and culture features over Factorial's payroll-supplement workflow.

FAQs

Specific to using Factorial HR API API through Jentic.

Why is there no official OpenAPI spec for Factorial HR API?

Factorial does not publish an OpenAPI specification — its developer reference is rendered as HTML at apidoc.factorialhr.com. Jentic generates and maintains this spec so that AI agents and developers can call Factorial HR API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Factorial HR API use?

Factorial uses HTTP Bearer authentication. Generate an API token from the workspace settings and pass it as Authorization: Bearer <token> on every call. Through Jentic the token is stored encrypted in the vault and injected at call time, so it never enters the agent's prompt context.

Can I run payroll itself with this API?

Not directly. The payroll surface in this version exposes /resources/payroll/supplements only — you can add bonuses, commissions, and other supplements that feed the next payroll cycle, but the actual payroll run is triggered inside the Factorial workspace by a payroll administrator.

What are the rate limits for the Factorial HR API?

Factorial does not document a numeric rate limit in the spec; limits are applied per workspace and surfaced via 429 responses when exceeded. Treat batch operations (e.g. employee list + per-employee document fetches) as paginated and back off on 429.

How do I create a time-off request through Jentic?

Run pip install jentic, then search Jentic for 'submit a time-off request', load the schema for POST /resources/time_off/leaves, and execute it with the employee ID, start_on, end_on, and the policy. Jentic injects the bearer token from your stored Factorial credentials. Sign up at https://app.jentic.com/sign-up.

Does the API expose the employee directory in real time?

Yes. GET /resources/core/employees returns the live employee directory and GET /resources/core/employees/{id} fetches a single record. Pair the list call with GET /resources/core/teams to recover reporting structure for downstream IAM or directory sync.