Localapi Jobadder JobAdder API

Name: JobAdder API
Brand: JobAdder API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingRecruiting Atsoauth295 EndpointsREST

For Agents

Read candidates, jobs, applications, placements, companies, and contacts from JobAdder, and look up reference data like statuses and custom fields, all over OAuth 2.0.

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Flocalapi.jobadder.com%2Fjobadder" | sh

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%2Flocalapi.jobadder.com%2Fjobadder" | 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.

Read candidate profiles, applications, placements, submissions, and notes from the recruitment database

Pull jobs, companies, and contacts with their custom fields and address records

Look up reference data lists like candidate ratings, sources, statuses, and salutations

GET STARTED

Start building with JobAdder API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use JobAdder API for, with concrete tasks.

★ Candidate Pipeline Reporting

Recruitment agencies need daily reporting on the candidate pipeline: how many candidates are at each status, which jobs are stuck, which placements closed. The JobAdder API exposes candidates, applications, placements, and reference status lists, so a reporting job can pull each collection and join them into the agency's BI tool. OAuth 2.0 with offline_access keeps the integration running without re-authentication.

Page through GET /candidates and GET /applications, join against GET /candidates/lists/status, and load into the warehouse for a daily pipeline dashboard.

Custom Career Site Backend

Recruitment teams that build their own career site can read open jobs and submit candidate enquiries against JobAdder's data model. The API exposes jobs, companies, contacts, candidates, and applications with custom fields, so the site can surface live JobAdder data without copying it into a separate database.

Call GET /candidates/{candidate_id}/applications/active to surface a candidate's live applications back on a self-service portal.

Recruiter CRM Sync

Agencies often run a separate CRM for client and contact relationships. The companies, contacts, and notes endpoints in JobAdder let an integration push activity from the CRM into the ATS, keeping recruiter activity logs in a single system. Custom fields are exposed so the agency's bespoke data model is preserved.

Call GET /companies/{company_id}/contacts and POST notes against the matching candidate or application from the CRM update.

AI Agent Recruitment Assistant

An AI agent assisting recruiters can answer questions like 'show me all candidates submitted for this job last week' by calling JobAdder via Jentic. The agent finds the right operation through Jentic's intent search, loads the schema, and executes - without holding the OAuth token or browsing JobAdder's docs.

Use Jentic to call GET /candidates/{candidate_id}/submissions for a named candidate and summarise the submission history for the recruiter.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/candidates

List candidates

GET

/candidates/{candidate_id}/applications

Applications for a candidate

GET

/applications

List applications

GET

/companies

List companies

GET

/candidates/{candidate_id}/placements

Placements for a candidate

GET

/candidates/lists/status

Reference list of candidate statuses

GET

/candidates

List candidates

GET

/candidates/{candidate_id}/applications

Applications for a candidate

GET

/applications

List applications

GET

/companies

List companies

GET

/candidates/{candidate_id}/placements

Placements for a candidate

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the JobAdder API by hand means running its OAuth 2.0 authorization-code flow, refreshing access tokens as they expire, and handling retries yourself against localapi.jobadder.com. Through Jentic you install once, import the JobAdder API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

JobAdder puts the candidate id in the URL path (/candidates/{candidate_id}/applications), so a rule can pin your agent to reads for one candidate, such as their applications or placements. Every operation here is a GET, so the agent reads the ATS data model and performs no writes.

Credential isolation

Your JobAdder access and refresh tokens are stored once, encrypted, by your own Jentic One instance, which refreshes the access token automatically and injects it at execution time. The refresh token and client secret never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list a candidate's applications', and Jentic returns the matching JobAdder operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using JobAdder API through Jentic.

Why is there no official OpenAPI spec for JobAdder API?

JobAdder does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call JobAdder API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the JobAdder API use?

JobAdder uses OAuth 2.0 authorization code flow against id.jobadder.com/connect/authorize. Access tokens last 60 minutes; request the offline_access scope to receive a refresh token. Through Jentic, the access and refresh tokens are stored encrypted and rotated automatically, so the agent never holds either.

Can I list all applications for a specific job?

Yes. JobAdder models applications as a top-level resource. Call GET /applications and filter by job and status reference list values from /applications/lists/status to narrow the results to a particular job and pipeline stage.

What are the rate limits for the JobAdder API?

Rate limits are not stated in the spec. JobAdder applies per-account limits at the contract level; agencies on higher tiers have higher quotas. Implement client-side backoff on 429 responses regardless.

How do I retrieve a candidate's submission history through Jentic?

Search Jentic for 'list a candidate's submission history'. Jentic returns the GET /candidates/{candidate_id}/submissions operation. Load the schema, supply the candidate ID, and execute. The response is the submission collection ready to render.

Does the API expose custom fields defined in JobAdder?

Yes. Candidates, applications, companies, and other major resources have dedicated custom fields endpoints (e.g. /candidates/fields/custom) that return both the field definitions and values, so an integration can preserve the agency's bespoke data model.

Can I limit what my agent is allowed to do with the JobAdder API?

Yes. Because your Jentic One instance is self-hosted, your own rules decide which JobAdder operations and credentials the agent may use. Every JobAdder operation exposed here is a GET, so the agent only reads the ATS data model and can never write to it. Since the candidate id sits in the URL path, such as GET /candidates/{candidate_id}/applications and GET /candidates/{candidate_id}/placements, you can pin the agent to reads for a single candidate rather than the whole account.