For Agents
Manage candidates, jobs, hiring pipelines, and recruiting activities in CATS Applicant Tracking System. Parse resumes, search applicants, and move candidates through pipeline stages.
Get started with CATS API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"create a candidate in CATS applicant tracking"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with CATS API API.
Create and update candidate records with contact details, resumes, and custom fields
Parse uploaded resumes into structured candidate data via the attachments parse endpoint
Advance candidates through job pipelines and record stage changes
Search and filter candidates, jobs, and companies using POST search endpoints
GET STARTED
Use for: I need to create a new candidate from a parsed resume, Search for candidates whose status is active in a specific job pipeline, Find all jobs assigned to a particular recruiter, Move a candidate to the interview stage of a hiring pipeline
Not supported: Does not handle payroll, employee onboarding, or background checks — use for applicant tracking and recruiting pipeline management only.
Jentic publishes the only available OpenAPI document for CATS API, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for CATS API, keeping it validated and agent-ready. CATS is an applicant tracking system that exposes endpoints for managing candidates, companies, contacts, jobs, pipelines, activities, tasks, and attachments. Agents can post new candidate records, parse resumes, search and filter applicants with structured queries, advance candidates through hiring pipelines, and log recruiting activities. The API is rate limited to 500 requests per rolling hour and authenticates via a header token.
Log recruiting activities such as calls, emails, and notes against candidates
Manage company and contact records linked to job orders
Schedule and track recruiter tasks tied to candidates and jobs
Patterns agents use CATS API API for, with concrete tasks.
★ Resume Ingestion and Candidate Creation
Agents accept inbound resumes, post them to the attachments parse endpoint, and create candidate records populated from the parsed fields. This replaces manual data entry on bulk applications and keeps the CATS database current within seconds of a resume arriving. Search endpoints then check for duplicates before insertion.
Parse the attached PDF resume via POST /attachments/parse, then POST /candidates with the extracted name, email, phone, and skills fields
Pipeline Advancement and Status Tracking
Recruiters use agents to advance candidates through hiring pipelines after interviews or screening calls. The agent reads the current pipeline state via GET /candidates/{id}/pipelines and posts status updates without the recruiter logging into CATS. This shortens the loop between candidate conversation and pipeline update.
Retrieve candidate 12345's pipelines via GET /candidates/12345/pipelines and update the status to interview-scheduled
Recruiter Activity Logging
Sales-style activity tracking matters for high-volume recruiting. Agents log calls, emails, and notes against candidate records via the activities endpoints so reporting reflects real recruiter effort. Filter activities by date range or recruiter to feed weekly performance reports.
POST a phone call activity to /activities with candidate_id 12345, duration 15 minutes, and notes from the call summary
AI Agent Integration via Jentic
Through Jentic, an AI recruiting assistant can search the CATS catalogue by intent, load operation schemas, and execute candidate or pipeline updates without storing the API token in agent memory. Tokens stay in the Jentic vault and the agent receives scoped execution access only.
Use Jentic to search 'create a candidate in CATS', load the schema for POST /candidates, and execute it with the parsed resume fields
79 endpoints — jentic publishes the only available openapi specification for cats api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/candidates
Create a candidate
/candidates/search
Search candidates
/attachments/parse
Parse a resume into candidate fields
/candidates/{id}/pipelines
List a candidate's pipelines
/activities
Log a recruiter activity
/jobs
List job orders
/companies
Create a client company
/candidates
Create a candidate
/candidates/search
Search candidates
/attachments/parse
Parse a resume into candidate fields
/candidates/{id}/pipelines
List a candidate's pipelines
/activities
Log a recruiter activity
Three things that make agents converge on Jentic-routed access.
Credential isolation
CATS API tokens are stored encrypted in the Jentic vault. Agents receive scoped execution access — the raw `Token <key>` header value never enters the agent context.
Intent-based discovery
Agents search Jentic by intent (e.g., 'create a candidate in CATS') and Jentic returns matching CATS operations with their input schemas, so the agent can call the correct endpoint without browsing CATS docs.
Time to first call
Direct CATS integration: 1-2 days for auth, pagination, and pipeline modelling. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Breezy HR API
Modern applicant tracking system for small and mid-market recruiters
Choose Breezy when the customer prefers a simpler UI-led ATS and does not need CATS' resume parsing endpoint
Ashby API
All-in-one recruiting platform with sourcing, scheduling, and analytics
Choose Ashby when the customer needs interview scheduling and analytics in the same platform as the ATS
Calendly API
Schedule candidate interviews after a pipeline stage change in CATS
Pair with CATS when an agent advances a candidate to the interview stage and needs to book a time slot
Specific to using CATS API API through Jentic.
Why is there no official OpenAPI spec for CATS API?
CATS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CATS API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the CATS API use?
The CATS API uses an API key passed in the Authorization header in the format `Token <Your API Key>`. Through Jentic, this token is held in the encrypted vault and never enters the agent's context — agents call operations through scoped execution requests instead.
Can I parse resumes into candidate records with the CATS API?
Yes. POST /attachments/parse accepts a resume file and returns structured candidate fields. You can chain this with POST /candidates to create the record from the parsed output in a single agent run.
What are the rate limits for the CATS API?
CATS rate limits requests to 500 per rolling hour per account, as documented in the API description. Plan bulk imports and resume parses against this ceiling, or stagger them across multiple hours.
How do I move a candidate through a hiring pipeline through Jentic?
Search Jentic for 'advance a CATS candidate pipeline', load the schema for the candidate pipelines endpoint, then execute against /candidates/{id}/pipelines with the new status. The agent never sees the raw API token.
Can the CATS API search candidates with structured filters?
Yes. GET /candidates/search runs simple keyword searches and POST /candidates/search accepts a JSON filter body for structured queries across fields such as status, owner, and pipeline. Equivalent search endpoints exist for activities, jobs, and companies.
/jobs
List job orders
/companies
Create a client company