Paylocity Jobs API.
A developer’s reference. Paylocity’s API is partner-gated, requires a customer sponsor, and is scoped to per-customer integrations rather than aggregation. Here is what the actual public surface looks like and when a unified jobs API saves you from the partner-program paperwork.
On this page
The short answer
Paylocity has a developer API, but the credentials are gated behind the Paylocity Partner Program - and the program is designed for per-customer integrations, not multi-tenant jobs aggregation. The application requires a Paylocity customer to sponsor your integration, a business review, and a technical review. Approval timelines run multi-month.
If you are building a jobs aggregator, sourcing tool, or hiring-signal intent product that needs Paylocity data across many customers, the partner program is not the right shape. Even after approval, your credentials are scoped to specific customer relationships.
The realistic options are: per-customer scrapers against the public careers widget (ongoing maintenance, shape-change risk), per-customer partner integrations (impractical for cross-tenant use), or a unified jobs API that handles the integration centrally.
Why the Partner Program is the gate
Paylocity is an enterprise HCM platform - their API model treats third-party vendors the way Salesforce treats AppExchange partners: as integrations on behalf of mutual customers, not as data consumers. The partner-program structure makes sense for recruiting CRMs, background-check vendors, or analytics tools that already have Paylocity-customer relationships.
It does not fit aggregation. Even after a successful application, Paylocity-issued credentials are scoped to the sponsoring customer’s tenant. To aggregate postings across the Paylocity customer base, you would need a separate sponsoring customer for each tenant you want to read - which collapses the multi-tenant use case entirely.
The actual public surface
Paylocity customers running the recruiting module publish job postings to customer-branded careers sites that embed a Paylocity careers widget. The widget renders job listings client-side from an internal JSON endpoint - reachable with a JSON fetch rather than HTML scraping, but undocumented and shape-sensitive to Paylocity releases.
Postings appear at recruiting.paylocity.com URLs (the Paylocity-hosted careers domain) or on customer-owned domains that embed the same widget. There is no list endpoint - each customer’s presence on Paylocity must be discovered through external means.
Why scraping breaks at scale
Discovery. Paylocity does not publish a customer directory. You build a list manually, by inspecting careers pages from companies you suspect are on Paylocity, or by maintaining a curated database. Coverage gaps are inevitable.
Shape drift. The careers-widget JSON endpoint changes between Paylocity releases without notice. What worked last quarter may return a different shape this quarter. Per-customer scraper configs become per-release maintenance burden.
Rate limits and protection. Paylocity rate-limits per-domain and runs CDN-level abuse protection. A scraper covering many customer subdomains gets blocked fast without IP rotation, polite cadences, and careful retry logic.
When to use a unified API instead
For per-customer integrations where you have a Paylocity-customer relationship - go through the Partner Program. That is the path Paylocity supports.
For multi-tenant aggregation - Paylocity postings across many customers, for a job board, sales triggers, or hiring-signal intent - JobsPipe handles the integration centrally. Every public Paylocity career site is indexed, normalized to the same JSON shape as Workday, Greenhouse, Lever, Indeed, and 30+ other sources, and served through one endpoint with one key. Free tier covers 5,000 requests/month with no partner application.
FAQ
Does Paylocity have a public jobs API?+
No. Paylocity's developer documentation lives at developer.paylocity.com, but credentials are gated behind the Paylocity Partner Program. Independent developers building an aggregator are out of scope - the program requires an active Paylocity customer to sponsor your integration, and the credentials you receive are scoped to per-customer integrations, not multi-tenant aggregation.
What is the Paylocity Partner Program?+
Paylocity's program for third-party software vendors who want to integrate with Paylocity on behalf of mutual customers - typically recruiting CRMs, background-check vendors, or analytics tools. Approval requires a sponsoring customer, a business review, and a technical review. Timeline is multi-month, and the resulting credentials are scoped to specific customer integrations.
Can I scrape Paylocity careers pages?+
Possible per customer. Paylocity-hosted careers sites embed a careers widget that renders postings client-side from an internal JSON endpoint. The endpoint is undocumented and changes between Paylocity releases. Per-customer config, ongoing shape-change maintenance, and IP rotation under Paylocity's per-domain rate limits are all required.
Where are Paylocity job postings published?+
On recruiting.paylocity.com URLs, on Paylocity-hosted customer subdomains, or embedded into customer-owned domains via the careers widget. There is no master list of Paylocity customers running the recruiting module - you discover each customer's surface independently.
How does JobsPipe handle Paylocity?+
JobsPipe indexes every public Paylocity careers site at scale, tracks the careers-widget shape changes centrally, and exposes the data alongside Workday, Greenhouse, Lever, BambooHR, and 30+ other sources in one normalized JSON schema. No partner application required. Free tier covers 5,000 requests/month.
What schema does JobsPipe return for Paylocity postings?+
Same shape as every other source: title, company, tenant (the Paylocity customer slug), location (city, region, country, remote flag), salary (parsed when explicitly stated), employment type, posted_at, expires_at, apply_url, and full description. You handle Paylocity records identically to Workday, Greenhouse, or any other source.
Does JobsPipe expose Paylocity payroll or HRIS data?+
No. JobsPipe is jobs-only. Paylocity payroll, time-and-attendance, benefits, and HRIS data are private to each customer and not in scope. Even when JobsPipe indexes a Paylocity-hosted careers site, only the public-facing postings are read.
How fresh is Paylocity data on JobsPipe?+
Public Paylocity career sites are re-crawled at least every 24 hours. New postings appear in the index within that window, and removed postings are dropped on the next cycle.
Every public Paylocity careers site, one endpoint. No partner program required.
Get a free API key