Frequently asked questions
The things worth knowing before you spend an afternoon in the docs. For anything deeper, each answer points at the page that goes further.
- Where does the data come from?
- Postings are read from employers' own public job boards — the Greenhouse, Lever or Workday instance a company runs for itself — rather than bought from an aggregator or resold from a third party. That provenance is the point: it's why apply_url is the employer's real application form, and why a posting disappears here when the employer takes it down. Sources & provenance
- How fresh is the data?
- Ingestion runs hourly. A new posting on a fast-tier board like Greenhouse, Ashby or Lever typically appears within the hour; heavier platforms such as Workday or iCIMS can take several. The whole pool of 100,000-plus boards is covered every few hours. Read `newest` from /v1/meta for the live freshness figure. Dataset coverage
- How is this different from an aggregator or LinkedIn?
- Two things. Provenance: postings come from employers' own boards, so apply_url is the real form, and the same job posted to several boards is collapsed to one row instead of returned five times. And the company join: every posting arrives with its hiring company's firmographics attached, so you don't resolve employer names yourself. The company join
- Do you have webhooks?
- No — the API is pull-based by design. Instead of pushing events, it exposes incremental feeds: new, expired and modified postings since a cutoff, which together cover a posting's full lifecycle. You poll them on your own schedule and keep a mirror in sync. Syncing the feed
- Can I redistribute or resell the data?
- You build products on top of the data under your plan. Bulk redistribution or reselling the raw dataset is a separate arrangement, not something the standard plans grant — the licensing guide and the Terms set out exactly what's included, and custom or flat-file delivery is available on request. Data licensing
- What's included in the free plan?
- 500 API requests a month, the full dataset, and every filter — no card required. Paid plans differ only in volume: more requests per month and a higher per-minute rate. There is no tier that unlocks extra data or extra filters. Pricing
- How complete is the salary data?
- About 36% of postings carry a parsed salary, because most employers simply don't publish a band. The API is honest about that rather than hiding it: /v1/meta publishes live per-field fill rates, so you can see exactly how much of any field is populated before you filter on it. Salary data
- How much do you cover?
- 64 sources — 63 ATS platforms plus LinkedIn — roughly 158,000 companies with firmographics, over 108,000 boards tracked, across about 597,000 live postings. Every one of those numbers moves constantly; /v1/meta reports the live counts, and hardcoding them is a mistake the docs warn against. Dataset coverage
- What fields does every posting carry?
- Title, the resolved hiring company, location, employment type, work arrangement, seniority, salary when it's published, extracted skills, the apply URL, the source board, and timestamps. The company resolves to a full profile on all but two postings in the entire dataset. The Job object
- Is there an uptime guarantee?
- The live status of the API, portal and billing is on the status page, with uptime measured over the days actually recorded rather than a window we haven't lived through yet. /v1/health is unauthenticated and fast enough to poll if you'd rather measure it yourself. Service status
- How do API keys work, and are they secure?
- A key is shown once, at creation, and stored only as a SHA-256 hash — the portal can't show it to you again, only revoke and replace it. Send it as a Bearer token from your backend; it must never be exposed in a browser, since anyone who sees it can spend your quota. Authentication
- How do I keep a local copy in sync?
- Use the feeds rather than paging the search endpoint to the end. /v1/jobs/feed returns everything new and changed since a cutoff; /v1/jobs/expired returns what came down so you can purge it. Page both with the keyset cursor, which stays fast at any depth. Syncing the feed