Source · JobAdderJobAdder Jobs API.
Public job postings from companies and agencies that use JobAdder, one endpoint - same schema as 30+ other sources.
Why people are confused about the JobAdder API
"JobAdder API" points at JobAdder's OAuth-authorized recruitment-CRM API (api.jobadder.com), scoped to a single account's jobs, candidates, placements, and applications. It is built to automate one recruiter's or agency's workflow, not to surface postings across every JobAdder customer.
JobAdder customers publish open roles to public job boards and careers pages, but there is no public endpoint that enumerates JobAdder accounts or their postings. JobsPipe indexes the public JobAdder-hosted postings it can identify and normalizes them into the same JSON shape as every other source.
Right for automating one account's jobs, candidates, and placements once that account authorizes your OAuth app. It is not a cross-account job feed.
Possible for a board whose URL you already know. Subject to rate limits, HTML drift, and no way to discover other accounts.
Public job postings from JobAdder-powered boards under one endpoint, normalized - no per-account OAuth, no board discovery.
JobAdder API documentation
JobAdder's developer documentation lives at api.jobadder.com and its developer portal. The API is OAuth-authorized and scoped to a single account, exposing that account's jobs, candidates, placements, and applications. It is not a public, cross-account job feed: there is no unauthenticated postings endpoint and no list endpoint to enumerate JobAdder customers. JobsPipe's normalized JSON schema is documented at /docs and uses the same shape across JobAdder, Workday, Greenhouse, and 30+ other sources.
Sample request
curl https://api.jobspipe.dev/v1/jobs/search \
-H "Authorization: Bearer jp_live_your_key_here" \
-H "Content-Type: application/json" \
-d '{ "source_or": ["jobadder"], "limit": 25 }'Sample response
{
"id": "ja_NDk2ZmEwMWItN2Fj",
"source": "jobadder",
"tenant": "peoplein",
"title": "Registered Nurse",
"company": "PeopleIN",
"location": {
"city": "Brisbane",
"region": "QLD",
"country": "AU",
"remote": false
},
"salary": {
"min": 85000,
"max": 105000,
"currency": "AUD",
"period": "year",
"source": "explicit"
},
"employment_type": "full_time",
"posted_at": "2026-05-15T02:30:00Z",
"expires_at": null,
"apply_url": "https://jobs.jobadder.com/peoplein/...",
"description": "PeopleIN is recruiting a Registered Nurse for a client facility in metropolitan Brisbane ..."
}Every JobAdder job record is returned in the same JSON shape as every other JobsPipe source. The full schema is documented in the docs.
Fields in every JobAdder job record
FAQ
Is there a JobAdder API for job postings?+
JobAdder has an OAuth-authorized API, but it is scoped to one account's jobs and candidates - not a public feed across every JobAdder customer. For public JobAdder-hosted postings across many accounts, JobsPipe is the aggregation layer.
How do I get JobAdder API credentials?+
Register an app in JobAdder's developer portal and have each account authorize it via OAuth - credentials see only that account's data. JobsPipe needs no JobAdder credentials: it consumes only public board postings and authenticates with one JobsPipe key.
Can I get jobs from one company that uses JobAdder?+
Yes. "company_name_partial_match_or": ["peoplein"] in the JSON body of POST /v1/jobs/search filters to that company's postings (substitute any company name).
Does JobsPipe expose JobAdder candidate data?+
No. JobsPipe reads only public job postings - never candidate, placement, or application data.
Try JobAdder data free - key in 30 seconds.
Get a free API key