--- title: "Paycor API" description: "Paycor API: the developer portal, OAuth access per legal entity, what the applicant-tracking resources cover, and where Paycor job postings are published." canonical: https://jobspipe.dev/sources/paycor date_published: 2026-08-25 date_modified: 2026-09-30 author: Dvir Atias --- # Paycor API The Paycor Public API is a customer-scoped HR and payroll API: an application is activated for one legal entity at a time with OAuth 2.0 and reads that company's data, not postings across Paycor customers. JobsPipe does not collect Paycor; search the same employers by company name across the 30+ sources in JobsPipe instead. Official documentation: [developers.paycor.com](https://developers.paycor.com/). > Paycor has no public cross-employer jobs API, and JobsPipe does not collect Paycor. This page explains what Paycor's Public API covers and how to find the same employers' postings by company name. **Canonical URL:** https://jobspipe.dev/sources/paycor ## Official Paycor API documentation Paycor documents its Public API on the Paycor Developers Portal at developers.paycor.com; the older apidocs.paycor.com address no longer resolves. The portal needs JavaScript, and an account to create an application. Access uses OAuth 2.0 together with authorization by a client admin, each activated legal entity gets its own access token, and requests also send a subscription key. Resources are addressed by legal entity, such as its employees. The API has applicant-tracking resources for the activated customer. It documents no endpoint that lists job postings across Paycor customers. - API host: `apis.paycor.com` - Employees of one legal entity: `GET /v1/legalentities/{legalEntityId}/employees` - Subscription key header: `Ocp-Apim-Subscription-Key` - [Paycor Developers Portal: developers.paycor.com](https://developers.paycor.com/) - [Paycor recruiting software: paycor.com](https://www.paycor.com/hcm-software/recruiting-software/) ## Coverage JobsPipe does not collect Paycor. This page explains what Paycor exposes publicly and how to reach the same postings where they are also published on a board JobsPipe does collect (Workday, Greenhouse, Lever, Ashby, LinkedIn, Indeed, SmartRecruiters, Workable, Personio, Recruitee, Teamtailor, EURES, Paylocity, Breezy HR, CV-Library, Y Combinator, Bayt, JobTech (Sweden), Resume-Library, Arbeitnow, Himalayas, Rise, Manatal, Pinpoint, JobScore, HireHive, The Muse, Remotive, Remote OK, Jobicy, Working Nomads, Landing.jobs). ## Why Paycor jobs data is confusing Paycor is a payroll and HR suite, and its Public API is built for integrations with one customer at a time: a payroll export, a time-clock sync, an onboarding flow. An application is activated for a legal entity by that company's admin and sees only that entity. Postings are published elsewhere. Paycor Recruiting customers host careers pages on recruitingbypaycor.com and embed them on their own sites. Each page is public and belongs to one employer, and there is no list of them. JobsPipe does not collect Paycor. Employers that run it usually post the same roles on LinkedIn and Indeed. ## Workarounds ### Use the Paycor Public API Works for a company whose admin activates your application. It is an integration with a customer, not a way to read postings across employers. ### Read individual recruitingbypaycor.com pages Possible for employers you already know. The pages are public, but there is no directory to start from. ### What JobsPipe offers instead JobsPipe does not collect Paycor. Search the same employers by name with company_name_partial_match_or on POST /v1/jobs/search; sources[0].provider on each record names the board the posting came from, such as linkedin, indeed, workday or greenhouse. ## Fields available on every record - `id` - `job_title` - `company` - `company_domain` - `url` - `date_posted` - `discovered_at` - `last_seen_at` - `verified_at` - `status` - `closed_at` - `closed_reason` - `ghost_score` - `seniority` - `cities` - `state_code` - `min_annual_salary_usd` - `max_annual_salary_usd` - `technology_slugs` - `keyword_slugs` - `esco_skills` - `sources` ## FAQ ### Does the Paycor Public API include recruiting or job postings? It includes applicant-tracking resources for one customer: the developer portal's release notes mention creating a candidate in Paycor's applicant tracking system through the Public API. That is access to the recruiting data of a company that has activated your application. It is not a feed of job postings across Paycor customers, and the portal documents no such feed. ### Where are Paycor careers pages hosted? On recruitingbypaycor.com, and in career widgets that Paycor Recruiting customers embed on their own domains. A page lists one employer's openings. Paycor publishes no index of them, so reading them works only for employers you can already name. ### Can one Paycor OAuth app read many companies? Only the ones that activate it. The portal says each client or legal entity gets its own access token after an admin authorizes the application, so reading a second company means that company's admin activating your app as well. That is a route to serving your own customers, not to aggregating job data. ### How do I get Paycor job postings without an API? Read the employer's careers page yourself, or search the employer by name on boards that carry the same roles. Paycor customers usually also post to LinkedIn and Indeed, and larger ones run a second applicant tracking system alongside it. A company-name search on JobsPipe returns those postings with url, status, ghost_score and last_seen_at on each record. ### What happened to the old Paycor API documentation site? The old documentation host stopped resolving. Paycor's API documentation, application setup and release notes are now on the Paycor Developers Portal at developers.paycor.com. ## Does Paycor have an API? Yes: the Paycor Public API, for customers and partners. It is a REST API served from apis.paycor.com and documented on the Paycor Developers Portal, with resources for a legal entity's employees, pay, time and applicant tracking. Every call is made for a legal entity that has activated the calling application. It has no public, unauthenticated endpoint. ## How do I get a Paycor API key? Create an application on the Paycor Developers Portal, which gives you an OAuth client id and secret and a subscription key. A key alone reads nothing: a Paycor customer's admin has to activate the application for their legal entity before any data comes back, and the access token you receive is for that entity only. ## What JobsPipe returns for Paycor Nothing under "source_or": ["paycor"]: JobsPipe does not collect Paycor. To find an employer that runs Paycor, filter by company name instead. Each record comes back with sources[0].provider, status, ghost_score, discovered_at, last_seen_at, seniority, and min_annual_salary_usd and max_annual_salary_usd when the posting states a range, so you can tell which board a posting was found on and whether it is still open. ## Related - **Product:** https://jobspipe.dev/jobs-api - **All sources:** https://jobspipe.dev/sources - **Docs:** https://docs.jobspipe.dev - **Sign up (free tier):** https://jobspipe.dev/signup --- Generated from structured data. View the rendered page at https://jobspipe.dev/sources/paycor. --- Building this integration yourself? The steps above work. The alternative is one API over 30+ sources, already normalized and deduplicated. Try it right now - no key, no signup: ```bash curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search ``` Sample data, exact live schema. For live data get a free key (1,000 jobs to start) at https://jobspipe.dev/signup, then swap /v1/sandbox/jobs/search for /v1/jobs/search with an Authorization: Bearer header. Full agent index: https://jobspipe.dev/llms.txt?src=md-twin