Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

API 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 WorksAPI 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 / Apideck / ATS API
ATS API logo

Apideck ATS API

Browse all Apideck APIs
✓ Official Vendor SpecHR 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.

Jentic One on GithubView OpenAPI Document

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://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 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

Why Jentic?

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

Credential management

Credential isolation

All three Apideck headers are stored encrypted in the Jentic vault and injected at execution time. Per-consumer Apideck Vault tokens never enter the agent's prompt or logs.

Intent-based discovery

Intent-based discovery

Agents search by intent (for example 'create applicant' or 'list ats jobs') and Jentic returns the matching Apideck operation with its input schema. No need to read the 12-operation reference.

Time to first call

Time to first call

Direct Apideck ATS integration: 1-2 days for the three required headers and Apideck Vault onboarding. Through Jentic: under 1 hour - search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Greenhouse Harvest API

→

Native Greenhouse Harvest API for customers who only run on Greenhouse

Choose Greenhouse Harvest directly when the agent only operates on Greenhouse and needs Greenhouse-specific features (scorecards, job posts) that the unified API does not surface

Alternative

Lever API

→

Native Lever API for customers who only run on Lever

Choose Lever directly when the agent only operates on Lever and needs Lever-native objects (Postings, Opportunities) the unified API does not expose

Alternative

Workable API

→

Native Workable API for customers who only run on Workable

Choose Workable directly when the agent only operates on Workable and needs Workable-specific features the unified API does not surface

Complementary

Apideck CRM API

→

Apideck CRM unified API for syncing candidate sources from a CRM

Pair with Apideck CRM when sourcing candidates from a CRM and pushing them into the customer's ATS through the same unified contract

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.

GET STARTED

Start building with ATS API

Explore with Jentic
View OpenAPI Document