Recruitee API
Official vendor OpenAPI document · agent-readyHR recruitingRecruiting Atsbearer85 EndpointsREST
For Agents
Programmatically create a candidate, list candidates. Covers 85 operations with bearer authentication.
Use for: I need to a candidate, I want to candidates, Search for a candidate, Find all a candidate
Not supported: Does not handle payments, communications, or crm - use for hr and recruiting only.
Recruitee is an Applicant Tracking System (ATS) and collaborative hiring platform. This API provides programmatic access to manage candidates, job offers, departments, pipeline stages, tags, notes, tasks, and placements within your Recruitee account. The API exposes 85 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Recruitee API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Recruitee 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%2Frecruitee.com%2Frecruitee" | sh2
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%2Frecruitee.com%2Frecruitee" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Recruitee API.
Create a candidate
List candidates
Get a candidate
Update a candidate
Delete a candidate
Merge candidates
Use Cases
Patterns agents use Recruitee API for, with concrete tasks.
★ HR and Recruiting Operations
Use the Recruitee API to perform hr recruiting operations programmatically. The API provides 85 endpoints covering core functionality including create a candidate, list candidates, get a candidate.
Call POST /candidates to create a candidate
Automated Candidates Management
Automate candidates operations by combining multiple Recruitee API endpoints. Agents can list candidates and then get a candidate in a single workflow.
Call GET /candidates to list candidates, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Recruitee 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 bearer tokens manually.
Search Jentic for 'create a candidate', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
85 endpoints — recruitee is an applicant tracking system (ats) and collaborative hiring platform.
METHOD
PATH
DESCRIPTION
POST
/candidates
Create a candidate
GET
/candidates
List candidates
GET
/candidates/{id}
Get a candidate
PATCH
/candidates/{id}
Update a candidate
DELETE
/candidates/{id}
Delete a candidate
GET
/candidates/{id}/duplicates
Get candidate duplicates
PATCH
/candidates/{id}/merge
Merge candidates
PATCH
/candidates/{id}/follow
Follow a candidate
POST
/candidates
Create a candidate
GET
/candidates
List candidates
GET
/candidates/{id}
Get a candidate
PATCH
/candidates/{id}
Update a candidate
DELETE
/candidates/{id}
Delete a candidate
GET
/candidates/{id}/duplicates
Get candidate duplicates
PATCH
/candidates/{id}/merge
Merge candidates
PATCH
/candidates/{id}/follow
Follow a candidate
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Recruitee API by hand means handling its bearer token auth and building every path under your company id host segment (/c/{company_id}). Through Jentic you install once, import the Recruitee API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Recruitee puts the candidate id in the URL path (/candidates/{id}), so a rule can pin your agent to specific candidates. You choose the operations it may call, so writes like merging or deleting a candidate are only included if you add them.
Credential isolation
Your Recruitee token 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.
Intent-based discovery
Agents search Jentic by intent such as 'create a candidate' or 'find duplicate candidates', and Jentic returns the matching Recruitee 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.
FAQs
Specific to using Recruitee API through Jentic.
What authentication does the Recruitee API use?
The Recruitee API uses a Bearer token 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 create a candidate with the Recruitee API?
Yes. Use the POST /candidates endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Recruitee 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 create a candidate through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a candidate'. Jentic returns the matching Recruitee API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Recruitee API have?
The Recruitee API exposes 85 endpoints covering candidates, offers, departments operations.
Can I limit what my agent is allowed to do with the Recruitee API?
Yes. Because you run Jentic One yourself, your own rules decide which Recruitee operations and credentials the agent can use. Recruitee puts the candidate id in the URL path, such as /candidates/{id}, so a rule can pin your agent to specific candidates, and you choose the operations it may call. Write actions like merging candidates via PATCH /candidates/{id}/merge or deleting one via DELETE /candidates/{id} are only available if you add them.
GET STARTED