Paylocity Job Postings API - JobsIndex by Aspen Tech Labs

Paylocity combines HR and payroll software with recruiting tools used by employers across the United States and beyond. This Actor provides structured access to jobs published through Paylocity-powered career sites.

The JobsIndex API, built by Aspen Tech Labs, collects 130K+ jobs directly from Paylocity-powered sources. It is part of a broader index aggregating 11M+ active job listings daily from 300K+ employer source sites globally.

Coverage is not limited by posting date. If a job was posted six months ago, a year ago, or longer, as long as it is an actual live job posting, we have it in our index. We actively verify that every position is current and not an abandoned posting. Our database also includes evergreen roles that companies keep open on a rolling basis, which we tag in the system.

What You Can Use It For

This Actor serves two primary use cases: teams that want to publish Paylocity job listings on their platform, and teams that need structured Paylocity ATS data for matching algorithms, AI model training, or tech hiring intelligence.

This Actor can power job boards and careers platforms with live Paylocity postings, and feed matching engines, AI models, and hiring intelligence tools with data filterable by role, location, or posting date.

Need More Or Something Different?

If this Actor is working well for you, we'd love a review. For more data, custom feeds, feedback, or any questions, reach out via our website or email. You can also explore JobMarketPulse, our labor and job market intelligence platform.

Built-In Search Preset

This Actor is fixed internally to Paylocity-powered jobs (ats_name=paylocity). The ATS/source platform preset is not exposed as an input parameter. Users can narrow the search by country, structured location, role keywords, salary, company, category, posting age, employment type, seniority, work arrangement, and pagination fields.

Quick Start

{
  "what": "@title software engineer",
  "country": "United States",
  "page": 0,
  "size": 5
}

Input Parameters

Parameter	Description	Example
salary	Salary amount or range filter.	20h-30h
what	Main job search query. Supports keywords, boolean logic, exact phrases, and field-targeted search such as @title software engineer or @(title,description) (python).	@title software engineer
where	Free-text location search. Supports place names, boolean logic, and field-targeted search such as @country United States or @(city,metro_area) (San Francisco). Prefer structured location fields for exact filters.	United States
country	Country filter.	United States
region	State, province, or region.	California
city	City filter.	San Francisco
postal_code	Postal or ZIP code filter.	94105
metro_area	Metropolitan area filter.	San Francisco-Oakland-Fremont, CA
title	Job title filter.	Software Engineer
company_name	Company name filter.	Example Employer
company_domain	Company website domain.	example.com
category	Job category.	Information Technology
sub_category	More specific job function or role.	Software Developer
industry	Company industry filter.	Software
remote	Work arrangement filter. Supported values: remote, on-site, hybrid.	remote
posted	Relative posting age or ISO date.	1w
employment_type	Employment type.	Full-Time
seniority	Seniority level.	Senior
page	Page number, starting from 0.	0
size	Number of results per page. Default 5, min 1, max 100.	5

Salary Filter Format

Use:

NUMBER[UNIT]

or:

NUMBER[UNIT]-NUMBER[UNIT]

Supported units:

• h - per hour
• d - per day
• w - per week
• m - per month
• y - per year

Examples:

• 20h-30h - hourly rate between 20 and 30
• 35h - fixed hourly rate
• 20h-200000y - range from hourly to yearly comparison

Advanced Filters

what and where support plain-text search, boolean logic, and field-targeted search.

If no field is provided, the API expands the search across a default set of relevant fields.

Plain keyword examples:

what = front end engineer
where = United States

Field-specific examples:

what = @title software engineer
where = @country United States

Multi-field examples:

what = @(title,description) (python)
what = @(title,title_raw,description) (engineer OR manager)
what = @(title,description) (machine AND learning)

where = @(country,region,city,metro_area,county,sub_city) (United States)
where = @(city,region,metro_area) (San Francisco OR California)
where = @(city,region,metro_area) (California)

Structured Filter Precedence

When using what or where, avoid sending separate structured filters for the same search unless you want those structured filters to take priority.

• For where, location fields such as country, region, city, postal_code, and metro_area take priority and can override or narrow the free-text location query.
• For what, structured job filters such as title, company_name, company_domain, category, sub_category, industry, posted, salary, employment_type, remote, and seniority take priority and can override or narrow the keyword query. For example, sub_category = Registered Nurse takes priority over what = engineer.

Use what and where as free-text searches when their corresponding structured filters are not set.

Common job/content fields for what:

• title, title_raw, description, reference
• category, sub_category, seniority, industry, company_type
• company_name, company_domain, company_name_raw
• employment_type, remote, language
• posted, posted_raw, expired
• url_source, url_apply
• salary_value, salary_currency, salary_unit
• id

Common location fields for where:

• country, region, city, metro_area, county, sub_city, postal_code

Location Filtering

For precise location matching, use structured filters exposed for this Actor:

• country
• region
• city
• postal_code
• metro_area

Use where only as a free-text location search when the structured location filters above are not set. If where is provided together with structured location filters, the structured filters take priority and where may be ignored or deprioritized.

Limits and Pagination

This Actor uses the JobsIndex jobs API. Results are paginated with page and size.

Parameter	Default	Min	Max
page	0	0	Depends on size and the item cap
size	5	1	100

Invalid page or size values can return 400 Invalid page or size parameters.

Item Caps

The maximum number of retrievable jobs depends on the query shape:

Query shape	Max items	Effective max size	Over-size behavior
No company filter	1000	100	Validation error; not silently capped
Company filter plus another keyword or filter	20	20	Silent cap with capping metadata
Company filter only	5	5	Silent cap with capping metadata

A company filter means company_name, company_domain, or a company field referenced inside what. Another keyword or filter means anything in what other than company_*, or a value in fields such as title, category, sub_category, industry, posted, salary, employment_type, or seniority where available on this Actor.

When a company-filtered request asks for size greater than the effective cap, the API returns up to the capped number of results instead of erroring. The response metadata includes:

• size_requested - the original requested size
• size_capped_by - "company" for the 5-item cap or "company|keywords" for the 20-item cap

On uncapped responses, size_requested and size_capped_by are not present.

No-company-filter requests are not silently capped. If the request exceeds the 1000-item retrieval window, the API can return 400 Item limit reached. Maximum of 1000 items can be retrieved.

Free-Text Query Limits

what and, where available, where support advanced matching syntax but have safety limits:

Limit	Value	Error behavior
Raw URL length before decoding	700 characters	400 'what' or 'where' parameters exceed 700 characters
Decoded text length	500 characters	400 MATCH input exceeds length limit
Combined operator characters: ?, +, pipe, @	20	400 Too many MATCH operators
Unsafe SQL-like keywords	blocked	400 Unsafe MATCH expression

Unsupported characters may be normalized before search. Unbalanced quotes and trailing @ characters may be stripped.

Field Validation

Invalid filter values can return 400 Invalid value for parameter: <name>. Common validation examples include malformed company domains, invalid dates or relative posted values, invalid salary format, invalid job IDs, unsupported location formats, or overly long field values.

ID Lookup Shortcut

When id is provided, the search query is bypassed and the API returns the matching job record or records. Job IDs must be numeric; otherwise the API returns 400 Invalid job id format.

Output

Each run stores job records in the default Apify dataset. The dataset schema includes an Overview table for the most useful fields and a Raw data (all fields) table for the complete JobsIndex record.

Example dataset item:

{
  "id": "1234567890123456789",
  "title": "Software Engineer",
  "company_name": "Example Employer",
  "company_domain": "example.com",
  "category": "Information Technology",
  "sub_category": "Software Developer",
  "country": "United States",
  "region": "California",
  "city": "San Francisco",
  "salary_value": null,
  "salary_currency": null,
  "salary_unit": null,
  "employment_type": "Full-Time",
  "remote": "n/a",
  "posted": "2026-06-22",
  "url_apply": "https://example.com/jobs/software-engineer"
}

Field availability depends on the source job posting.