Officient API

Name: Officient API
Brand: Officient API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingEmployee Managementoauth298 EndpointsREST

For Agents

Read and update Officient employee, contract, time-off, expense, and asset records, and subscribe to HR events through webhooks.

Install Jentic One Beta

Connect the Officient API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Officient 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: 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 Officient API.

List employees and read individual personnel profiles with contracts and wages

Submit and approve calendar requests for time off and absences

Manage employee assets, fleet vehicles, and assigned documents

GET STARTED

Start building with Officient API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Officient API for, with concrete tasks.

★ Payroll-input synchronisation

Pull current wage, contract, and expense data from Officient into a payroll engine each cycle. The API exposes per-person wage and expense endpoints, plus contract listings, so payroll operators can produce a complete monthly input file without re-keying. This compresses the prep step from a half-day spreadsheet exercise to an automated job.

List all active employees, fetch current wage for each, sum approved expenses for the month, and produce a payroll-input CSV

Automated onboarding

When a new hire is created in an ATS, push the record into Officient and generate a self-service invitation link so the employee fills in their personal details directly. Combined with department and team endpoints, this can also place the new hire on the org chart and assign starting assets.

Create a person record in Officient, generate a self-service invite link, and assign the new hire to a department and team

Time-off and absence reporting

Submit, list, and report on calendar requests for sick leave, vacation, and other absences. Managers can approve requests through the API, and downstream BI dashboards can pull the calendar request history to track absence patterns by team. The webhook channel lets messaging tools post a notification when a request lands.

List all calendar requests in pending state, approve those from a specific manager's direct reports, and post a Slack notification per approval

Asset and fleet tracking

Track laptops, phones, and company vehicles assigned to each employee through the assets and fleet endpoints. When an employee leaves, list their assets and trigger a return workflow; when a new hire starts, assign the standard kit. The fleet endpoints expose vehicle detail for company cars and fuel cards.

Retrieve all assets assigned to a leaving employee and create a return ticket for each in the IT helpdesk system

AI agent HR assistant via Jentic

An HR-facing AI agent uses Jentic to answer questions like 'who is on leave next week?' or 'what is the wage history for employee 42?' The agent searches Jentic for the right Officient operation, loads the schema, and executes through OAuth credentials managed in the Jentic vault.

Search Jentic for 'list calendar requests', load the schema, and execute it for the next 7 days filtered to a specific department

Key Endpoints

98 endpoints — officient api is the integration surface for officient's hris, used to manage personnel records, contracts, payroll inputs, time off, expenses, assets, fleet, and performance reviews.

METHOD

PATH

DESCRIPTION

GET

/1.0/people/list

List employees in the company

POST

/1.0/token

Exchange OAuth credentials for an access token

GET

/1.0/wages/{person_id}/current

Get current wage for an employee

POST

/1.0/people/selfservice/invite_link

Generate a self-service invitation link for a new hire

GET

/1.0/assets/list

List company-issued assets

GET

/1.0/fleet/{vehicle_id}/detail

Get fleet vehicle detail

GET

/1.0/wages/{person_id}/history

Get wage history for an employee

GET

/1.0/people/list

List employees in the company

POST

/1.0/token

Exchange OAuth credentials for an access token

GET

/1.0/wages/{person_id}/current

Get current wage for an employee

POST

/1.0/people/selfservice/invite_link

Generate a self-service invitation link for a new hire

GET

/1.0/assets/list

List company-issued assets

Why Jentic?

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

Credential isolation

Officient OAuth client secrets are stored encrypted in the Jentic vault. Tokens are minted and refreshed by Jentic; the agent never holds the client secret or long-lived refresh token directly.

Intent-based discovery

Ninety-eight endpoints across 15 resources require careful navigation. Agents search Jentic by intent (for example 'list employees on leave next week') and Jentic returns the right calendar-request endpoint with its input schema ready.

Time to first call

Direct integration including OAuth bootstrapping, schema reading, and webhook setup: 2-3 days. Through Jentic: under 1 hour.

FAQs

Specific to using Officient API through Jentic.

What authentication does the Officient API use?

The API uses OAuth 2.0. Obtain an access token via the /1.0/token endpoint and pass it as a bearer credential on subsequent calls. Through Jentic, the OAuth client is stored encrypted in the vault and tokens are refreshed automatically, so the raw client secret never enters the agent's context.

Can I list all employees with the Officient API?

Yes. GET /1.0/people/list returns the employee directory. Per-person endpoints under /1.0/people/{id} and /1.0/wages/{person_id}/current expose contract, wage, and contact details. Combine with /1.0/contracts to read employment-history records.

What are the rate limits for the Officient API?

Officient applies per-token rate limits but does not publish exact thresholds in the spec. Excessive requests return 429 with a Retry-After hint. For bulk syncs, batch by department or team rather than iterating one person at a time, and respect the Retry-After value before resuming.

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

Search Jentic for 'submit calendar request', load the schema for the calendar-request POST operation, and execute with the person_id, start and end dates, and request type. Jentic handles the OAuth bearer and returns the created request ID.

Does the Officient API support webhooks for HR events?

Yes. The Webhook resource lets you register endpoints for HR lifecycle events. Subscribed URLs receive a JSON payload when the event fires, which you can route into Slack notifications, payroll reconciliation, or audit logs.

Can I generate a self-service invitation link for a new hire?

Yes. Use POST /1.0/people/selfservice/invite_link with the person_id to generate a one-time link the new hire follows to fill in personal data, upload a contract signature, and set up self-service access. This removes the manual step of HR transcribing onboarding forms.

Officient API

Connect the Officient API to your agent

Capabilities

Start building with Officient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs