# Paycom Jobs API

> Every public Paycom career site, one endpoint. No per-customer credentials, no scraper to maintain.

**Canonical URL:** https://jobspipe.dev/sources/paycom

## Coverage

- **Sources covered:** 5,000+ Paycom customers
- **Freshness:** 24h refresh
- **History retention:** 12 months retention

## Why Paycom jobs data is confusing

Paycom does not offer a public aggregator API for job postings. Paycom's Client API is private - only accessible to active Paycom customers, and only for that customer's own data. If you want to consume jobs across many Paycom-using companies, there is no first-party path.

Paycom customers host their careers pages on subdomains of paycomonline.net (the most common pattern) or on their own domains via Paycom-managed embeds. The underlying job data is reachable via a public HTML rendering, but there is no consistent JSON endpoint across customers. JobsPipe normalizes that data into the same schema we use for Workday, Indeed, and every other source.

## Workarounds

### Scrape paycomonline.net subdomains

Technically possible. Each customer is a separate scraper config, the HTML changes occasionally, and you'll need IP rotation to stay under Paycom's per-domain rate limits.

### Sign API agreements with each Paycom client

Each customer would need to grant you Client API access individually. Impractical for any cross-company use case.

### Use JobsPipe

Every public Paycom careers site, one endpoint. Same schema as 30+ other sources.

## Fields available on every record

- `id`
- `source`
- `tenant`
- `title`
- `company`
- `location`
- `salary`
- `employment_type`
- `remote`
- `posted_at`
- `expires_at`
- `apply_url`
- `description`

## Sample response

```json
{
  "id": "pc_aXNoeWFobGFvaW1zbm",
  "source": "paycom",
  "tenant": "bigcorp",
  "title": "Payroll Operations Specialist",
  "company": "Big Corp Holdings",
  "location": {
    "city": "Oklahoma City",
    "region": "OK",
    "country": "US",
    "remote": false
  },
  "salary": {
    "min": 55000,
    "max": 72000,
    "currency": "USD",
    "period": "year",
    "source": "explicit"
  },
  "employment_type": "full_time",
  "posted_at": "2026-05-12T15:01:00Z",
  "expires_at": null,
  "apply_url": "https://bigcorp.paycomonline.net/v4/ats/...",
  "description": "Big Corp Holdings is hiring a Payroll Operations Specialist to support multi-state payroll processing ..."
}
```

## FAQ

### Does JobsPipe need Paycom Client API credentials?

No. JobsPipe pulls only public-facing careers data - what any anonymous visitor to paycomonline.net can see. We never have access to private Paycom Client API endpoints.

### How fresh is Paycom data on JobsPipe?

Every Paycom customer's careers site is refreshed at least every 24 hours.

### Are Paycom jobs deduped against other sources?

Yes. If the same posting appears on Paycom and on a separate company careers page or Indeed, JobsPipe links them as the same canonical job record.

### Which Paycom plans does JobsPipe cover?

JobsPipe indexes Paycom Talent Acquisition customers using paycomonline.net (and customer-owned domains running Paycom embeds). Internal-only postings are not crawled.

## Paycom API documentation

Paycom's developer documentation is gated behind active customer credentials and accessible only via the Paycom Online portal under the Client Action Center. There is no public-facing developer documentation indexed by Google because Paycom does not offer a third-party-accessible Client API - by design, it's a closed customer-only surface. JobsPipe's documentation at /docs covers the normalized JSON shape we return for every Paycom careers site, alongside 30+ other ATSs in the same schema.

## Paycom API key

Paycom Client API keys are minted by the customer's Paycom administrator inside Client Action Center under Tools > Integrations. Each key is scoped to a single Paycom tenant - no cross-tenant developer key, no public sandbox, no self-service signup. JobsPipe doesn't need Paycom credentials at all. We consume only public Paycom careers pages and authenticate every request with one JobsPipe API key.

## Paycom API integration

Single-tenant Paycom integration (sync payroll, employees, time-off for one customer) requires that customer to mint you Client API credentials. Cross-tenant aggregator integration - what most teams arriving on this page actually need - is JobsPipe: one API key, every public Paycom careers site, same JSON schema as 30+ other ATSs.

## In-depth guides

- https://jobspipe.dev/guides/paycom-jobs-api

## Related

- **Product:** https://jobspipe.dev/jobs-api
- **All sources:** https://jobspipe.dev/sources
- **Docs:** https://jobspipe.dev/docs
- **Sign up (free tier):** https://jobspipe.dev/signup

---
Generated from structured data. View the rendered page at https://jobspipe.dev/sources/paycom.