Humi Ca Humi Partners API

Name: Humi Partners API
Brand: Humi Partners API
Availability: InStock

✓ Official Vendor SpecHR recruitingEmployee Managementbearer4 EndpointsREST

For Agents

Read Humi employee records and time-off entries through the partner API, scoped by the customer-issued token.

Install Jentic One Beta

Connect the Humi Partners API to your agent

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

List every employee on a Humi account that the partner token can see

Retrieve a single employee record by Humi employee ID

List all time-off entries across the company within the token's scope

GET STARTED

Start building with Humi Partners API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Humi Partners API for, with concrete tasks.

★ Roster sync into a partner application

Mirror the customer's Humi employee directory into a partner application — for example a benefits platform or learning system — so the customer does not have to maintain two rosters. The list endpoint returns paginated employee records following JSON:API conventions, which the partner walks once on connect and then refreshes on a schedule.

Call GET /v1/employees, follow the JSON:API next-page links until exhausted, and upsert each record into the partner system keyed by Humi employee ID.

Time-off-aware scheduling

Read approved time-off from Humi so a downstream scheduling, payroll, or project management tool can avoid scheduling people who are out. The time-off endpoints support both a global view and per-employee filtering so the partner system can refresh efficiently when only one person's plans change.

Call GET /v1/timeoff/{employeeId} for the employee, then exclude their unavailable dates from the scheduling tool's allocation grid.

Compliance and headcount reporting

Pull the Humi employee list as a periodic snapshot for compliance reporting or headcount dashboards that need an authoritative HR source. Because the API enforces partner-token scopes, only the data the customer has authorised flows out, which keeps audit boundaries tidy.

Call GET /v1/employees, snapshot the result with a timestamp, and emit a row per employee into the reporting warehouse.

Agent-driven Humi reads through Jentic

An agent fielding HR questions like 'who is out next Friday?' uses Jentic to find the Humi time-off operation, loads the schema, and returns the answer. Jentic injects the customer-issued partner token from the vault so the agent never sees the raw credential.

Through Jentic, search 'list Humi time-off', load the schema for GET /v1/timeoff, and execute it filtered to the requested date range.

Key Endpoints

4 endpoints — the humi partners api gives third-party applications read access to employee and time-off data on a humi hr account.

METHOD

PATH

DESCRIPTION

GET

/v1/employees

List employees on the account

GET

/v1/employees/{employeeId}

Retrieve a single employee record

GET

/v1/timeoff

List all time-off entries

GET

/v1/timeoff/{employeeId}

List time-off entries for a single employee

GET

/v1/employees

List employees on the account

GET

/v1/employees/{employeeId}

Retrieve a single employee record

GET

/v1/timeoff

List all time-off entries

GET

/v1/timeoff/{employeeId}

List time-off entries for a single employee

Why Jentic?

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

Credential isolation

Humi partner tokens are stored encrypted in the Jentic MAXsystem vault, scoped per customer install. Agents call partner operations through execution handles so the raw Bearer token never enters the agent's prompt context.

Intent-based discovery

Agents search by intent like 'list Humi employees' or 'list Humi time-off' and Jentic returns the matching partner operation with its full input schema, including pagination and per-employee filters.

Time to first call

Direct integration: 1-2 days for partner token onboarding, JSON:API pagination, and rate-limit handling. Through Jentic: under 30 minutes — search, load, execute the read operation.

FAQs

Specific to using Humi Partners API through Jentic.

What authentication does the Humi Partners API use?

Each customer issues a Humi partner token from their account, and the partner sends it as a Bearer header. Through Jentic the per-customer token sits in the encrypted MAXsystem vault and is injected at execution time so the agent never holds the raw token.

Can I write back to Humi through this API?

No. The Humi Partners API is read-only — it covers listing employees, fetching a single employee, and reading time-off entries. Writes happen inside Humi's own UI or admin surfaces.

What are the rate limits for the Humi Partners API?

Humi applies per-token rate limits and recommends keeping calls under a few requests per second. Use JSON:API pagination rather than retry storms when walking the full employee list.

How do I list time-off through Jentic?

Search Jentic for 'list Humi time-off', load the schema for GET /v1/timeoff, and execute it. Jentic returns the parsed JSON:API resource collection with pagination cursors ready for the agent to iterate.

Does the API expose payroll or pay-stub data?

No. Pay-related fields are not exposed on the partner API. The current surface is limited to employee directory fields and time-off entries.

Why are some employees missing from my list response?

The partner token's scope is set by the customer when they install the integration. If specific employees are missing, the customer needs to broaden the integration's scope inside Humi before they appear in API responses.