Migrating from Fantastic.jobs
Our feed endpoints accept the same paths, parameters and pagination as the Fantastic.jobs v1 ATS endpoints and return jobs with the same field names, so most integrations only need a new base URL and key.
Endpoints
| Endpoint | Status | Notes |
|---|---|---|
| /v1/active-ats | Supported | Same time frames (1h, 24h, 7d, 6m), limit/offset/cursor, search and date filters. |
| /v1/active-ats-count | Supported | Including time_frame=1m. |
| /v1/modified-ats | Supported | modified_fields is null. |
| /v1/expired-ats | Supported | 1h, 1d, 1m, 6m. |
| /v1/ats-organizations | Supported | Returns employer names with their sources, countries and job counts instead of LinkedIn fields. |
| /v1/active-jb, /v1/expired-jb | Not offered | No job-board feed: we don't collect LinkedIn, Wellfound or Y Combinator listings. |
| /v1/ats-organizations-advanced | Not offered | No third-party company profiles. |
Differences to check
- Coverage: Canada and the United States. Every job has a
countryfield, andcountry=CA/country=USfilters by it. - Freshness:
1hreturns the last full UTC hour, available two minutes after it ends, rather than the hour before it. - No AI or LinkedIn fields:
ai_*,org_linkedin_*,org_crunchbase_*andclassification_*are not returned, and filters on them (ai_work_arrangement,organization_size,domain…) return400. Useremote=truefor remote jobs andinclude_source_fields=truefor the employer's own structured facts.include_basic_organization_detailsandinclude_betaare accepted and add nothing. - Always null:
organization_url,organization_logo,domain_derived,counties_derived,timezones_derived,location_requirements. - Values:
employment_typeusesFULL_TIME-style codes;sourceuses our system names (leverrather thanlever.co; the old names are accepted as filters); timestamps end inZ. - Locations: the same
City, Region, Countryform; codes after a city (Toronto, ON) are also accepted. - Errors are the same
application/problem+jsonshape, and unknown parameters are rejected with a suggestion. - Usage headers are named
x-jobs-*andx-requests-*; see Errors, limits & usage.
Ids are different from Fantastic's: re-key your stored jobs with a backfill rather than mixing the two.