canonical: https://jentic.com/apis/pubapi.talenthr.io/talenthr

# Pubapi Talenthr TalentHR API

The TalentHR API provides tools and resources to integrate TalentHR with internal software. Manage employees, job positions, time off, benefits, assets, documents, and more. The API exposes 169 endpoints secured with basic authentication.

## For AI agents

Programmatically get all system's timezones, get all languages. Covers 169 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- Get all system's timezones
- Access TalentHR API resources via REST API
- Access TalentHR API resources via REST API

## Use cases

### HR and Recruiting Operations

Use the TalentHR API to perform hr recruiting operations programmatically. The API provides 169 endpoints covering core functionality including get all system's timezones, get all languages, get all countries.

Example prompt: Call GET `/v1/timezones` to get all system's timezones

### Automated Applicant Tracking System Management

Automate applicant tracking system operations by combining multiple TalentHR API endpoints. Agents can get all languages and then get all countries in a single workflow.

Example prompt: Call GET `/v1/languages` to get all languages, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TalentHR API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Example prompt: Search Jentic for 'get all system's timezones', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/timezones` | Get all system's timezones |
| GET | `/v1/languages` | Get all languages |
| GET | `/v1/countries` | Get all countries |
| GET | `/v1/nationalities` | Get all nationalities |
| GET | `/v1/education-levels` | Get the education Levels |
| GET | `/v1/employment-statuses` | Get the employment statuses |
| GET | `/v1/relationship-types` | Get the relationship types |
| POST | `/v1/employees/hire` | Create an employee (Hire) |

## Key resources

- **Applicant Tracking System** — Operations related to Applicant Tracking System
- **Applicant Tracking System (Job Positions)** — Operations related to Applicant Tracking System (Job Positions)
- **Assets** — Operations related to Assets
- **Benefit** — Operations related to Benefit
- **Benefit (Categories)** — Operations related to Benefit (Categories)

## Why Jentic

- **Setup:** Wiring the TalentHR API by hand means encoding basic auth on every request and navigating its large set of lookup and employee endpoints yourself. Through Jentic you install once, import TalentHR from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** With TalentHR you limit the agent to the operations it needs, such as reading reference lists like timezones or countries. You choose the operations it may call, so writes like hiring an employee are not included unless you add them.
- **Credential handling:** Your TalentHR API credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list supported timezones' or 'hire an employee', and Jentic returns the matching TalentHR operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### What authentication does the TalentHR API use?

The TalentHR API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get all system's timezones with the TalentHR API?

Yes. Use the GET `/v1/timezones` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the TalentHR API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get all system's timezones through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get all system's timezones'. Jentic returns the matching TalentHR API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the TalentHR API have?

The TalentHR API exposes 169 endpoints covering applicant tracking system, applicant tracking system (job positions), assets operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which of the TalentHR API's 169 operations and which stored credential the agent may use. You can restrict it to read-only reference calls such as GET `/v1/timezones` or GET `/v1/countries`, so a write like POST `/v1/employees/hire` is off limits unless you explicitly add it. The agent only ever calls the operations you grant.