Skip to main content
POST
Search for job postings

Authorizations

pubrio-api-key
string
header
required

A unique API token that represents the actions you perform through the API and the corresponding permissions and operations. You can create it through the Settings section.

Body

application/json
locations
string[]

ISO 3166-1 alpha-2 (cca2) is used for filtering locations. Check out location endpoints under the Filters tab for more information.

Example:
exclude_locations
string[]

ISO 3166-1 alpha-2 (cca2) location codes to exclude from job results. Check out the location endpoints under the Filters tab for valid codes.

Example:
location_ids
integer[]

Posting country by Pubrio location_id (Locations endpoint; also on each row). Alternative to locations.

Example:
company_locations
string[]

The location of the company headquarters. Check out location endpoints under the Filters tab for more information.

Example:
companies
string<uuid>[]

A list of unique identifiers (domain_search_id) used for company and people search operations.

domains
string[]

List of company domains used for company and people search operations. If we receive a URL such as www.pubrio.com or https://docs.pubrio.com/, the system will convert it to pubrio.com for processing.

Example:
linkedin_urls
string[]

The fully formed URL of the LinkedIn company profile. URL begin with http and contain linkedin.com/company/

Example:
search_term
string

A string of words over which we want to filter the results.

Example:

"pubrio"

search_terms
string[]

Array of keyword strings to filter job postings. Each term is matched against job content. Use search_term for a single string or search_terms for multiple keywords.

Example:
titles
string[]

Job titles associated with the individuals you aim to locate.

The results will also encompass job titles that include similar terminology, even if they do not match exactly. For instance, searching for software engineer may yield results for individuals with the title senior software engineer.

Example:
functions
string[]

Function slugs derived from the title, e.g. engineering, sales, marketing, finance, product_management, or a Department Functions slug such as software_development, in any case. Unknown slugs match nothing. Full list: Enums & Constants.

Example:
departments
string[]

Department slugs or names, e.g. master_sales or Sales (any case), from Departments. Matches jobs whose title carries any of them; a value the catalog does not name matches nothing.

Example:
exclude_departments
string[]

Department slugs or names to leave out. A job with no department is kept.

Example:
seniority_ranks
enum<integer>[]

Seniority tier from the title: 1 junior, 2 senior, 3 manager, 4 director, 5 executive. A value outside 1–5 matches nothing. Rows return their tier in seniority_rank (0 = unclassified).

Available options:
1,
2,
3,
4,
5
Example:
posted_dates
string[]

Date range of the posted date. The maximum value is the current day. Day boundaries follow your workspace timezone.

Example:
launch_dates
string<date>[]

Inclusive [from, to] window (UTC) on the launch date: posting_date, or the ingestion day when absent. Matches how Job Insights counts. A single date matches that day.

Required array length: 1 - 2 elements
Example:
created_at
string<date-time>

Ingested at or after this instant (UTC). Date or ISO timestamp. For incremental syncs pass the created_at of your newest stored row.

Example:

"2026-09-02T12:00:00Z"

is_realtime_enrichment
boolean
default:false

Opt into realtime enrichment for a single, company-scoped query (filtered by domain_search_id, domains, or linkedin_urls). When the initial search returns zero results, the endpoint scrapes the source, persists the records, and re-runs the search before responding. Subject to a per-route deadline.

Example:

true

is_ascending_order
boolean
default:false

Sort direction. Results are returned newest-first by default; set true for oldest-first. There is no sort_by on this endpoint — the sort key is fixed and stated in the endpoint description.

Example:

false

per_page
integer
default:25

Records per page. Defaults to 25, which is also the ceiling on most plans — the limit is your subscription's max_search_per_page, returned by Profile. Exceeding it returns HTTP 416 with code 41676 (or 41613 on company and people search), not a clamped result set.

Required range: x <= 25
Example:

25

page
integer
default:1

Page number, starting at 1. The ceiling is your subscription's max_search_page (max_company_search_page for company search), returned by Profile. Exceeding it returns HTTP 416.

Example:

1

Response

Successful response containing company job search details.

metadata
object

Request context.

data
object
Last modified on June 1, 2025