Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / HR recruiting / Officient API
Officient API logo

Officient API

0
AI ReadinessNon-Ready (F)0/100
See full scorecard
Community OpenAPI document · agent-readyHR recruitingEmployee Managementoauth298 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to list all active employees in the company, Get the current wage for a specific employee, Submit a time-off request on behalf of an employee, Retrieve the contract history for employee 123

Not supported: Does not run payroll calculations, recruit candidates, or handle benefits enrolment - use for Officient HRIS records, time off, and expense management only.

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. Ninety-eight endpoints cover people, contracts, calendar requests, expenses, vehicles, documents, departments, and webhooks. Use it to sync employee data into payroll or BI systems, automate onboarding and offboarding, and trigger workflows from HR events.

Jentic One on GithubView OpenAPI Document

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.

1

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%2Fofficient.io%2Fofficient" | sh
2

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%2Fofficient.io%2Fofficient" | 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

Record and categorise employee expenses for reimbursement

Subscribe to HR events through webhooks for downstream automation

Read department, team, and cost-unit structures for org-chart sync

Generate self-service invitation links to onboard new hires

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 your Jentic One instance.

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

GET

/1.0/fleet/{vehicle_id}/detail

Get fleet vehicle detail

GET

/1.0/wages/{person_id}/history

Get wage history for an employee

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

O

Officient API

- Non-Ready (F)
0/100
49
Foundational Compliance
69
Developer Experience & Jentic Compatibility
11
AI-Readiness & Agent Experience
85
Agent Usability
0
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
49

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4
84%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

10%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

69

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4
52%

Example Density

How richly the API is illustrated with examples.

74%

Example Validity

Percentage of examples that conform to their schemas.

49%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

11

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
18%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

26%

Summary Coverage

Coverage of summaries across operations/tags/info.

85

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1
85%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

0

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
0%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

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

Setup

Wiring the Officient API by hand means running its OAuth flow, refreshing tokens, and navigating 98 endpoints across people, wages, assets, fleet, and calendar yourself. Through Jentic you install once, import Officient from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

Officient puts the person id in the URL path (for example /1.0/wages/{person_id}/current), so a rule can pin your agent to one person's records, and across the wider surface you limit it to the operations it needs, such as listing people or reading time off. You choose the operations it may call, so a wage read is not included unless you add it.

Credential isolation

Your Officient OAuth client credentials are stored once, encrypted, by your own Jentic One instance, which mints and refreshes tokens and injects them at execution time. The client secret and refresh token never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list employees on leave next week', and Jentic returns the matching Officient calendar operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Personio API

→

European HRIS with similar people, time-off, and payroll-input scope as an alternative to Officient

Choose Personio when the company already runs on Personio. Choose Officient when the company is on Officient - feature scope is similar but the data lives in different systems.

Alternative

BambooHR API

→

US-leaning HRIS alternative with employee records and time-off endpoints

Use BambooHR for US-based teams; Officient is more common in Belgian and Western European markets.

Complementary

Gusto API

→

Payroll engine that ingests employee and wage data the Officient API exports

Use Gusto to actually run payroll once Officient has supplied the wage and expense inputs; Officient itself does not run pay cycles in all jurisdictions.

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.

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

Yes. Because you self-host Jentic One, your own rules decide which Officient operations and credentials the agent may use, so you can allow only the calls it needs, such as GET /1.0/people/list or reading time-off requests, and leave everything else out. Officient puts the person id in the URL path, for example /1.0/wages/{person_id}/current, so a rule can pin the agent to a single person's records. A sensitive call like a wage read is never included unless you explicitly add it, and the OAuth credentials stay under your control.

GET STARTED

Start building with Officient API

Explore with Jentic One
View OpenAPI Document