Recruitis.io
Agent-ready OpenAPI document · curated by JenticHR recruitingRecruiting Atsbearer62 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Lets an AI agent run recruiting workflows in Recruitis: posting jobs, tracking candidates and answers, managing tasks and referrals, and reading reports.
Use for: I need to post a new job opening in Recruitis, Add a candidate to a job's pipeline, Retrieve the details of a specific job posting, Schedule an interview for a candidate
Not supported: Covers recruiting and applicant tracking only; it does not run payroll or manage employees after hire, so pair it with an HR system for post-hire workflows.
Jentic publishes the only available OpenAPI specification for Recruitis.io, keeping it validated and agent-ready. The Recruitis API drives an applicant tracking system over REST. It manages job postings and their publication channels, creates and tracks candidates and their answers, handles comments, tasks, referrals, and interview scheduling, and reads recruiting reports. Most operations use a bearer token, while the login and an enums endpoint need no token.
Install Jentic One Beta
Connect the Recruitis.io to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Recruitis.io, 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%2Fapp.recruitis.io%2Frecruitis" | 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%2Fapp.recruitis.io%2Frecruitis" | 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 Recruitis.io API.
Create job postings and manage their publication channels
Create candidates and track their answers and communication
Manage comments, tasks, and referrals on the hiring pipeline
Schedule interviews and manage reservation links
Read recruiting reports and the activity feed
Look up enums such as offices, sources, and reject reasons
Use Cases
Patterns agents use Recruitis.io API for, with concrete tasks.
★ Sync job postings to other channels
Recruiting teams publish the same opening across several boards. The Recruitis API creates jobs and manages the channels each job is published to, so an integration can open a role and push it to the right channels without touching the UI.
Create a job posting and add it to the requested publication channels.
Automate candidate intake
Applications arrive from many sources and need to land in one pipeline. The API creates candidates, records their answers, and tracks communication, so an integration can capture an applicant and attach them to the right job automatically.
Create a candidate against a job and record their submitted answers.
Report on hiring activity
Managers need visibility into pipeline health. The API reads recruiting reports, the activity feed, and tasks, so an integration can assemble a hiring dashboard or a weekly summary from live data.
Pull the recruiting report and summarize open jobs and recent activity.
Let an agent run recruiting tasks
An AI agent assisting a recruiter can post jobs, add candidates, and schedule interviews on request. Through Jentic the agent discovers these operations by intent and runs them under the recruiter's own bearer token, keeping actions inside the team's controls.
Given a candidate and a job, add the candidate and schedule an interview.
Key Endpoints
62 endpoints — jentic publishes the only available openapi specification for recruitis.
METHOD
PATH
DESCRIPTION
GET
/jobs
List job postings
POST
/jobs
Create a job posting
GET
/jobs/{id}
Get a job posting by id
POST
/candidates
Create a candidate
GET
/me
Get the authenticated user
GET
/tasks
List tasks in the pipeline
GET
/referrals
List referrals
GET
/reports
Read recruiting reports
GET
/jobs
List job postings
POST
/jobs
Create a job posting
GET
/jobs/{id}
Get a job posting by id
POST
/candidates
Create a candidate
GET
/me
Get the authenticated user
GET
/tasks
List tasks in the pipeline
GET
/referrals
List referrals
GET
/reports
Read recruiting reports
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Recruitis into an agent yourself means reading the generated spec, tracking the bearer token, and chaining the job, candidate, and enum calls. With Jentic you install once, import Recruitis from the Directory, and store the token a single time.
Permission scoping
Running Jentic in your own instance, you decide which Recruitis operations the agent may call, so you can allow reading jobs and candidates while blocking job creation or deletions. Access is granted per operation.
Credential isolation
Your Recruitis bearer token is held encrypted by your own Jentic One instance and injected only when an operation runs, so it never appears in the agent's prompt, logs, or context.
Intent-based discovery
Agents find Recruitis through Jentic's intent search: a request like add a candidate to a job resolves to the right operation with inputs and auth prepared.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Recruitis.io API through Jentic.
Is there an MCP server for the Recruitis API?
You do not need a dedicated MCP server. Through Jentic your self-hosted agent can call Recruitis operations directly by intent, so you connect the API without maintaining separate MCP tooling.
Can I restrict what my agent is allowed to do in Recruitis?
Yes. Because you run Jentic yourself, you choose which Recruitis operations your agent can call, so you can allow reading jobs and candidates while withholding job creation or deletions. Scoping is applied per operation.
What authentication does the Recruitis API use?
Recruitis uses a bearer token sent in the Authorization header. Most operations expect the token, while the login and an enums call do not. Jentic injects the token from your stored credential when a call runs.
Why is there no official OpenAPI spec for Recruitis.io?
Recruitis.io does not publish its own machine-readable OpenAPI definition, so Jentic generated this specification from the service and keeps it validated so agents can call the API reliably.
Can the API both post jobs and manage candidates?
Yes. The API covers the full pipeline: it creates and reads job postings and their channels, and it creates candidates, records their answers, and tracks communication and tasks.
How does an agent find Recruitis operations in Jentic?
The agent searches Jentic by intent, such as adding a candidate to a job, and Jentic returns the matching Recruitis operations ready to run under your token.
GET STARTED