canonical: https://jentic.com/apis/talentlyft.com/talentlyft

# TalentLyft Customers API

TalentLyft is an innovative recruitment software that streamlines the hiring process, from sourcing candidates to applicant tracking. It offers powerful tools for recruiters and HR professionals to attract, evaluate, and hire top talent efficiently. With features like job posting, candidate management, and customizable workflows, TalentLyft helps companies build their dream teams with ease. The API exposes 66 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get articles, get article. Covers 66 operations with apiKey authentication.

## Scope

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

## Capabilities

- Get articles
- Create Candidate
- Edit candidate
- Updates candidate's tags
- Monitor TalentLyft Customers API operational status and events

## Use cases

### HR and Recruiting Operations

Use the TalentLyft Customers API to perform hr recruiting operations programmatically. The API provides 66 endpoints covering core functionality including get articles, get article, create candidate.

Example prompt: Call GET `/v2/articles` to get articles

### Automated Candidates Management

Automate candidates operations by combining multiple TalentLyft Customers API endpoints. Agents can get article and then create candidate in a single workflow.

Example prompt: Call GET `/v2/articles/{id}` to get article, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TalentLyft Customers 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 apiKey tokens manually.

Example prompt: Search Jentic for 'get articles', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v2/articles` | Get articles |
| GET | `/v2/articles/{id}` | Get article |
| POST | `/v2/candidates` | Create Candidate |
| GET | `/v2/candidates` | Get candidates |
| GET | `/v2/candidates/{id}` | Get candidate |
| PUT | `/v2/candidates/{id}` | Edit candidate |
| PUT | `/v2/candidates/{id}/tags` | Updates candidate's tags |
| PUT | `/v2/candidates/{id}/skills` | Updates candidate's skills |

## Key resources

- **Candidates** — Operations related to Candidates
- **Jobs** — Operations related to Jobs
- **Departments** — Operations related to Departments
- **Employees** — Operations related to Employees
- **Pipelines** — Operations related to Pipelines

## Why Jentic

- **Setup:** Wiring the TalentLyft Customers API by hand means sending a JWT in the Authorization header on every call and threading candidate ids through nested tag and skill routes yourself. Through Jentic you install once, import the TalentLyft Customers API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** TalentLyft puts the candidate id in the URL path (`/v2/candidates/{id}/...`), so a rule can pin your agent to one candidate: it can read that candidate and nothing else. You choose the operations it may call, so updating a candidate or their tags and skills is not included unless you add it.
- **Credential handling:** Your TalentLyft key 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 'get articles' or 'create a candidate', and Jentic returns the matching TalentLyft 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 TalentLyft Customers API use?

The TalentLyft Customers API uses an API key passed in the `Authorization` header. 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 articles with the TalentLyft Customers API?

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

### What are the rate limits for the TalentLyft Customers 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 articles through Jentic?

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

### How many endpoints does the TalentLyft Customers API have?

The TalentLyft Customers API exposes 66 endpoints covering candidates, jobs, departments operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which TalentLyft operations and credentials the agent can use. Since TalentLyft puts the candidate id in the URL path (`/v2/candidates/{id}/...`), you can pin the agent to a single candidate and let it only read that record. Write operations like editing a candidate or updating their tags and skills stay off unless you explicitly add them to the agent's allowed set.