Humi Partners API

Name: Humi Partners API 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.

Quickstart

Get started with Humi Partners API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list Humi employees"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Humi Partners API 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

List time-off entries for a specific employee by ID

Iterate through paginated employee and time-off results following JSON:API cursors

GET STARTED

Start building with Humi Partners API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Humi Partners API 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 though 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.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

BambooHR

Mid-market HRIS with broader read and write coverage of employee data

Choose BambooHR when the integration needs write access to employee records or richer field coverage than Humi's partner API exposes.

Alternative

Rippling

All-in-one HR, IT, and finance platform with deeper API surface across modules

Pick Rippling when the customer needs HR plus device, app, and payroll integration in one platform.

Alternative

Deel

Global HR and contractor management with strong international payroll coverage

Choose Deel when the workforce is distributed across many countries and needs contractor and EOR coverage.

Complementary

Gusto

US-focused payroll provider commonly paired with HR data sources for the pay run

Use Gusto for the payroll run on top of the employee list mirrored from Humi.

FAQs

Specific to using Humi Partners API 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.