Official vendor OpenAPI document · agent-readyHR recruitingRecruiting AtsapiKey12 EndpointsREST
For Agents
Read jobs, applicants, applications, and offers across Greenhouse, Lever, Workable, and other ATS platforms through one unified schema.
Use for: List all open jobs in the connected ATS, Find an applicant by email address, Create an applicant record from a sourcing tool, Post a new application linking an applicant to a job
Not supported: Does not handle payroll, performance reviews, or HRIS employee records - use for recruiting hand-off (jobs, applicants, applications, offers) only.
Apideck ATS is a unified API that maps a single schema for jobs, applicants, applications, offers, and activities onto downstream applicant tracking systems such as Greenhouse, Lever, Workable, SmartRecruiters, and BambooHR. The 12 operations cover the recruiting hand-off most apps need: read open roles, read candidate records, post applications, and write offers. Apideck routes each call through Apideck Vault, so per-customer ATS credentials stay in Apideck's vault rather than being passed to the calling app.
Install Jentic One Beta
Connect the ATS API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ATS 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%2Fapideck.com%2Fapideck-ats" | 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%2Fapideck.com%2Fapideck-ats" | 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 ATS API.
List open job requisitions across many ATS platforms with consistent fields for title, department, and status
Read and write applicant records including name, contact, source, and resume URL
Post applications linking an applicant to a job with stage and source metadata
Read offers attached to an application with salary and start date
Read recruiting activities (notes, interviews, calls) attached to applicants
Filter and paginate the same way across every connected ATS connector
Use Cases
Patterns agents use ATS API for, with concrete tasks.
★ Sourcing-Tool to ATS Hand-Off
Push candidates from a sourcing or LinkedIn outreach tool into whichever ATS the customer uses. Apideck's /ats/applicants and /ats/applications endpoints accept the unified candidate payload and create the applicant on the connected ATS - Greenhouse, Lever, Workable, or SmartRecruiters. Sourcing vendors typically replace 4+ direct ATS integrations with a single Apideck contract this way.
POST a new applicant to /ats/applicants with name and email, then POST to /ats/applications linking that applicant to the open job_id
Job Distribution
Read open requisitions from a customer's ATS and republish them to a careers site, job board, or referral platform. /ats/jobs returns the unified job payload with department, location, and status, so a job-board syndication tool builds one integration that works against every supported ATS.
GET /ats/jobs?status=open and republish each open requisition to a careers microsite via the site's CMS
Recruiting Analytics
Pull applications, applicants, and offers from many customers' ATS instances into a single recruiting analytics warehouse. Apideck normalises the stage and status fields, so a funnel report (applied, screened, interviewed, offered, hired) works identically whether the underlying ATS is Greenhouse or Lever. Useful for talent-intelligence vendors and HR analytics tools.
GET /ats/applications with cursor pagination and store stage transitions so a downstream funnel report can render time-to-hire by source
AI Agent Recruiter Assistant
Give an AI agent a tool to find candidates, post applications, and check offer status across whichever ATS a customer uses. Through Jentic, the agent searches for an intent like 'create an applicant in customer ats' and gets the matching Apideck operation with its input schema. The agent does not need a per-ATS adapter.
Search Jentic for 'create ats applicant', load the /ats/applicants schema, and execute with the candidate's name and email captured from the conversation
Key Endpoints
12 endpoints — apideck ats is a unified api that maps a single schema for jobs, applicants, applications, offers, and activities onto downstream applicant tracking systems such as greenhouse, lever, workable, smartrecruiters, and bamboohr.
METHOD
PATH
DESCRIPTION
GET
/ats/jobs
List open requisitions on the connected ATS
GET
/ats/jobs/{id}
Read a single requisition by id
GET
/ats/applicants
List applicants on the connected ATS
POST
/ats/applicants
Create an applicant record
GET
/ats/applications
List applications with stage and source filters
POST
/ats/applications
Post a new application linking an applicant to a job
GET
/ats/jobs
List open requisitions on the connected ATS
GET
/ats/jobs/{id}
Read a single requisition by id
GET
/ats/applicants
List applicants on the connected ATS
POST
/ats/applicants
Create an applicant record
GET
/ats/applications
List applications with stage and source filters
POST
/ats/applications
Post a new application linking an applicant to a job
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
ATS API
- AI-Aware (B)64/100
52
Foundational Compliance85
Developer Experience & Jentic Compatibility58
AI-Readiness & Agent Experience94
Agent Usability50
Security53
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
52
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: C-Signals: 4
96%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
14%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
85
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: ASignals: 4
67%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
58
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C+Signals: 4
65%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
67%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
53
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: CSignals: 1
53%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Apideck ATS API by hand means setting up its API key plus consumer and service headers, learning the unified job and applicant shapes, and normalising across recruiting platforms yourself. Through Jentic you install once, import Apideck ATS from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Apideck ATS API puts the job id in the URL path (/ats/jobs/{id}) while applicants and applications are created via the request body, so scope the agent to the operations it needs, such as listing jobs and reading a job, and leave out creating applicants unless you add it. You choose the allowed operations, so the agent only calls what you list.
Credential isolation
Your Apideck API key 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 'list open jobs' or 'read an applicant's applications', and Jentic returns the matching Apideck ATS 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 ATS API through Jentic.
What authentication does the Apideck ATS API use?
Apideck requires Authorization with a bearer API key, x-apideck-app-id with your Unify application id, and x-apideck-consumer-id with the end-customer reference stored in Apideck Vault. Through Jentic all three values are stored encrypted in the vault and injected at execution time.
Which ATS platforms does the Apideck ATS API cover?
Apideck Unify routes ATS calls to connectors including Greenhouse, Lever, Workable, SmartRecruiters, BambooHR, and JazzHR. Use the x-apideck-service-id header to pin the call to a specific connector when a consumer has more than one connected.
Can I create an applicant with the Apideck ATS API?
Yes. POST to /ats/applicants with the unified applicant payload (first_name, last_name, emails, phone_numbers). Apideck translates the call into the native applicant on the connected ATS and returns the created record with the connector's id.
What are the rate limits for the Apideck ATS API?
Apideck enforces limits at both the Unify layer and the underlying connector. Greenhouse, Lever, and Workable each have their own per-token quotas, so an /ats/applicants call ultimately respects the downstream connector's limits. Expect ConnectorRateLimitError on connector throttling and HTTP 429 on Unify throttling - retry with backoff.
How do I post a new application through Jentic?
Search Jentic for 'post ats application', load the /ats/applications schema, and execute with applicant_id and job_id. The response returns the created application id from the connected ATS.
Is the Apideck ATS API free?
Apideck Unify offers a free tier with capped requests; production use is billed per consumer connection. See https://www.apideck.com/pricing for current tiers.
Can I limit what my agent is allowed to do with the Apideck ATS API?
Yes. Because you run Jentic One yourself, your own rules decide which Apideck ATS operations and credentials the agent may use. You can allow read-only calls such as listing jobs (GET /ats/jobs) and reading a single requisition (GET /ats/jobs/{id}) while leaving out write operations like creating an applicant (POST /ats/applicants) or posting an application (POST /ats/applications) unless you add them. The agent can only call the operations you list, and your Apideck key stays with your instance rather than the agent's context.
GET STARTED