canonical: https://jentic.com/apis/app.recruitis.io/recruitis # Recruitis.io 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. ## For AI agents Lets an AI agent run recruiting workflows in Recruitis: posting jobs, tracking candidates and answers, managing tasks and referrals, and reading reports. ## Scope 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. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: Given a candidate and a job, add the candidate and schedule an interview. ## Key endpoints | 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 | ## Key resources - **Jobs** — Job postings and their publication channels - **Candidates** — Candidate records, answers, and communication - **Tasks** — Tasks and referrals in the hiring pipeline - **Calendar** — Interview scheduling and reservation links - **Reports** — Recruiting reports and the activity feed ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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 - **SmartRecruiters** — Provides an enterprise applicant tracking and recruiting platform. - **Recruitee** — Offers collaborative hiring and applicant tracking over an API. - **TalentLyft** — Adds recruitment marketing and sourcing tools over an API. ## FAQ ### 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.