JobAdder API

Name: JobAdder API
Brand: JobAdder API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingRecruiting Atsnone95 EndpointsREST

For Agents

Drive a deep JobAdder ATS surface with 95 endpoints for applications, candidate floats and submissions, jobs, job ads, placements, notes, users, and user groups.

Install Jentic One Beta

Connect the JobAdder API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the JobAdder 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.

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

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

Manage applications including custom fields, status lists, and per-application notes via /applications and its nested routes

Maintain candidate floats and submissions to clients via /candidates float and submission resources

Create and manage job ads (board postings) separately from underlying job records via /jobs/ads

GET STARTED

Start building with JobAdder API

Explore with Jentic

View OpenAPI Document

This is an extended SwaggerHub-published spec for the JobAdder ATS, exposing 95 endpoints across applications, candidates, candidate floats and submissions, companies, contacts, jobs, job ads, job applications, placements, notes, users, and user groups. Compared to the smaller official 19-endpoint v2 surface, this spec includes deeper coverage of pipeline operations (custom fields, status lists, application notes) and administration resources (users, user groups). The base URL targets a localapi.jobadder.com host typical of partner sandbox environments, and the spec does not declare a security scheme — production calls require the standard JobAdder OAuth 2.0 token added by the integrator.

Use Cases

Patterns agents use JobAdder API for, with concrete tasks.

★ Candidate Float and Submission Workflow

Recruitment agencies float candidates to client contacts proactively and track which clients have been shown which candidates. The candidate-floats and candidate-submissions resources expose this workflow with endpoints to create, list, and update floats and submissions per candidate, which the smaller official v2 surface does not cover at the same depth.

POST a candidate float for candidateId=123 against companyId=456 with a marketing summary, then GET candidate floats for that candidate to confirm the record exists.

Custom Fields and Pipeline Customisation

Agencies customise their pipeline with bespoke statuses and custom fields. The /applications/fields/custom and /applications/lists/status endpoints expose those configurations programmatically so an integration can read the actual list of statuses (rather than hard-coding strings) before progressing applications.

GET /applications/lists/status to read the configured pipeline stages, then PATCH /applications/{id} to move the application to the next stage by id.

Multi-Recruiter User and Group Administration

Agencies with several teams need to provision recruiter accounts and assign them to user groups that map to permissions and workload routing. The /users and /user-groups endpoints let an automation onboard new recruiters into JobAdder when an HR system creates them, and offboard them when access ends.

GET /users to list recruiters, then POST a user-group membership change to move a recruiter from the perm desk group to the contract desk group.

AI Agent Integration via Jentic

An AI recruiting agent uses Jentic to discover the right JobAdder operation for the user's intent. With 95 endpoints in this spec, semantic search is essential — the agent searches Jentic for 'float a candidate to a client' and Jentic returns the right candidate-floats POST operation rather than the agent guessing among similar endpoints.

Search Jentic for 'float a candidate to a client', load the matching POST schema, and execute it for the chosen candidate and client company.

Key Endpoints

95 endpoints — this is an extended swaggerhub-published spec for the jobadder ats, exposing 95 endpoints across applications, candidates, candidate floats and submissions, companies, contacts, jobs, job ads, job applications, placements, notes, users, and user groups.

METHOD

PATH

DESCRIPTION

GET

/applications

List applications

GET

/applications/{application_id}

Read a single application

GET

/applications/fields/custom

List configured application custom fields

GET

/applications/lists/status

List configured application statuses

GET

/applications/{application_id}/notes

List notes on an application

GET

/applications

List applications

GET

/applications/{application_id}

Read a single application

GET

/applications/fields/custom

List configured application custom fields

GET

/applications/lists/status

List configured application statuses

GET

/applications/{application_id}/notes

List notes on an application

Why Jentic?

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

Credential isolation

JobAdder OAuth tokens are stored encrypted in the Jentic vault and injected into the Authorization header at execution time. Raw tokens never enter the agent's prompt context.

Intent-based discovery

Agents search Jentic with intents like 'float a candidate to a client' and Jentic returns the right operation among the 95 in this spec, avoiding the need for the agent to scan endpoint lists.

Time to first call

Direct integration against this larger spec: 3-7 days for OAuth and to model the deeper resources. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using JobAdder API through Jentic.

What authentication does this JobAdder API surface use?

The spec itself does not declare a security scheme (it was published to SwaggerHub without one), but production JobAdder API calls require an OAuth 2.0 access token from id.jobadder.com sent as Authorization: Bearer <token>. Through Jentic the OAuth flow is brokered and tokens are kept in the vault.

Can I float a candidate to a client with this JobAdder API?

Yes. The candidate-floats and candidate-submissions resources expose endpoints to create and list floats and submissions per candidate. This deeper agency-workflow coverage is the main reason to prefer this 95-endpoint spec over the leaner official 19-endpoint v2 surface.

What are the rate limits for the JobAdder API?

JobAdder applies per-account rate limits documented in the partner portal. Treat 429 responses as the trigger to back off, and paginate through list endpoints rather than requesting everything at once. The status and custom-field list endpoints can be cached because they change infrequently.

How do I read configured application statuses through Jentic?

Run pip install jentic, search for 'list jobadder application statuses', then load and execute GET /applications/lists/status. Cache the response and reuse it when progressing applications by id rather than hard-coding stage names.

How does this spec differ from the official jobadder.com main API?

This SwaggerHub-published spec covers 95 endpoints versus 19 in the official jobadder.com/main spec. The extra coverage is mostly around candidate floats and submissions, custom fields, application status lists, application notes, and user/user-group administration. Use this spec when an integration needs that deeper agency workflow; use the official spec for the core recruiting surface.

Is the JobAdder API free?

API access is included with paid JobAdder accounts. Partner integrations may have additional review or commercial steps documented in the JobAdder partner portal.