Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

Jentic OneSelf-hosted, open-source control plane between your agents and any APIAPI DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples
Resources
BlogLatest articles and insightsPress & MediaBrand assets and press contactOpen StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksJentic OneAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHub
BlogPress & MediaOpen StandardsNewsletter
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs / HR recruiting / CATS API
CATS API logo

Catsone CATS API

★ Only Publicly Available OpenAPI DocumentHR recruitingRecruiting AtsapiKey79 EndpointsREST

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.

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 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.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the CATS API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CATS 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 CATS 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

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

Use Cases

Patterns agents use CATS 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

Key Endpoints

79 endpoints — jentic publishes the only available openapi specification for cats api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/candidates

Create a candidate

GET

/candidates/search

Search candidates

POST

/attachments/parse

Parse a resume into candidate fields

GET

/candidates/{id}/pipelines

List a candidate's pipelines

POST

/activities

Log a recruiter activity

GET

/jobs

List job orders

POST

/companies

Create a client company

POST

/candidates

Create a candidate

GET

/candidates/search

Search candidates

POST

/attachments/parse

Parse a resume into candidate fields

GET

/candidates/{id}/pipelines

List a candidate's pipelines

POST

/activities

Log a recruiter activity

GET

/jobs

List job orders

POST

/companies

Create a client company

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential management

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

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

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.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

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

Alternative

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

Complementary

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

FAQs

Specific to using CATS 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.

GET STARTED

Start building with CATS API

Explore with Jentic
View OpenAPI Document