Source · PaycorPaycor Jobs API.
Every public Paycor Recruiting careers page, one endpoint. No per-customer OAuth onboarding.
Why people are confused about the Paycor API
The official Paycor Public API (apidocs.paycor.com) is an HR/payroll integration surface: per-customer OAuth credentials, scoped to one company's own data. Its documentation covers employees, pay, and time - it is not a public feed of job postings across Paycor customers.
Paycor Recruiting customers host their public careers pages on recruitingbypaycor.com and embedded career widgets. The public postings are there, but there is no cross-customer endpoint that enumerates them. JobsPipe indexes every public Paycor Recruiting careers page and normalizes the postings into the same schema as our other sources.
Right if you are integrating with one company's own Paycor account and they grant you OAuth credentials. Not a path to postings across many employers.
Technically possible. Each customer is its own page structure and pagination, and you own the drift when the widget markup changes.
Every public Paycor Recruiting customer, one endpoint, same JSON schema as 30+ other sources. Free tier included.
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": ["paycor"], "limit": 25 }'Sample response
{
"id": "pc_ZjA4MmQxYTYtM2Ix",
"source": "paycor",
"tenant": "midwest-health",
"title": "Registered Nurse - ICU",
"company": "Midwest Health Partners",
"location": {
"city": "Columbus",
"region": "OH",
"country": "US",
"remote": false
},
"salary": {
"min": 74000,
"max": 92000,
"currency": "USD",
"period": "year",
"source": "explicit"
},
"employment_type": "full_time",
"posted_at": "2026-08-20T14:05:00Z",
"expires_at": null,
"apply_url": "https://recruitingbypaycor.com/career/JobIntroduction.action?...",
"description": "Midwest Health Partners is hiring an ICU Registered Nurse for our Columbus campus ..."
}Every Paycor job record is returned in the same JSON shape as every other JobsPipe source. The full schema is documented in the docs.
Skip the scraper - try the API right now
Live, normalized postings from Paycor and 30+ other sources in one JSON schema. No key, no signup - this sandbox returns sample data in the exact live shape.
Press Test search to see normalized job records rendered here, and the raw JSON on the right.
POST /v1/sandbox/jobs/search{
"job_title_or": [
"software engineer"
],
"limit": 3,
"remote": true
}Advanced: edit the raw request, or copy it as curl
curl -X POST https://api.jobspipe.dev/v1/sandbox/jobs/search \
-H "Content-Type: application/json" \
-d '{"job_title_or":["software engineer"],"remote":true,"limit":5}'For live results, get a free key (1,000 jobs/month) and swap /v1/sandbox/jobs/search for /v1/jobs/search with an Authorization: Bearer header - request and response shapes are identical.
Fields in every Paycor job record
FAQ
Is there official Paycor API documentation for job postings?+
Paycor documents its Public API at apidocs.paycor.com, but it is a per-customer OAuth integration for HR data - not a public job-postings feed. For postings across Paycor customers, JobsPipe is the aggregated path.
Does JobsPipe need Paycor credentials?+
No. JobsPipe consumes only public-facing Paycor Recruiting careers data. No OAuth, no per-customer onboarding.
How fresh is Paycor data?+
Every public Paycor Recruiting careers site is re-crawled at least every 24 hours.
Are Paycor jobs deduped against other sources?+
Yes. When the same posting also appears on Indeed or LinkedIn, JobsPipe links them as one canonical job record with per-source attribution.
Try Paycor data free - key in 30 seconds.
Get a free API key