How Fantastic.jobs API Works
The Fantastic.jobs API is designed for platforms requiring high quality job posting data on regular intervals. For example, a job board pulling new listings every hour, or a newsletter pulling the last 24 hours once per day.
The primary source of this API are jobs sourced from ATS platforms (company career pages). We currently check over 200,000 companies from 54 ATS plaforms + Google, Meta, Apple, and Amazon for new jobs every hour.
We also index jobs from several job boards: LinkedIn, Wellfound, and Y Combinator. Some of our customers use these jobs to supplement the ATS jobs, while others are interested exclusively in jobs from job boards. Linkedin jobs for English speaking countries and Tech roles are indexed hourly as well, whereas jobs from other LinkedIn nations, Wellfound, and YCombinator are indexed with a couple hours of delay.
For details on how credits are consumed, tracked, and what happens on overage, see Credit Usage.
On-demand vs recurring requests
This API is designed for recurring requests where the results are stored in your own database. We do have customers querying the endpoints directly in response to end-user actions, but there are several trade-offs to be aware of:
- This API has a lot of parameters for searching and filtering, but these are "regular" keyword searches. While some parameters have options for wildcards we don't provide keyword expansion, semantic search, synonyms, or similarity. As a job board you might have a need for more advanced matching.
- Latency can be an issue for user-facing applications as complex searches can take several seconds
- On-demand requests often return overlapping results across users, while recurring requests only return new jobs, so on-demand becomes credit-expensive once you have many users issuing similar queries.
For these reasons we recommend moving to recurring requests as soon as possible, preferably once you move past the MVP stage.