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

EndpointStatusNotes
/v1/active-atsSupportedSame time frames (1h, 24h, 7d, 6m), limit/offset/cursor, search and date filters.
/v1/active-ats-countSupportedIncluding time_frame=1m.
/v1/modified-atsSupportedmodified_fields is null.
/v1/expired-atsSupported1h, 1d, 1m, 6m.
/v1/ats-organizationsSupportedReturns employer names with their sources, countries and job counts instead of LinkedIn fields.
/v1/active-jb, /v1/expired-jbNot offeredNo job-board feed: we don't collect LinkedIn, Wellfound or Y Combinator listings.
/v1/ats-organizations-advancedNot offeredNo third-party company profiles.

Differences to check

  • Coverage: Canada and the United States. Every job has a country field, and country=CA / country=US filters by it.
  • Freshness: 1h returns 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_* and classification_* are not returned, and filters on them (ai_work_arrangement, organization_size, domain…) return 400. Use remote=true for remote jobs and include_source_fields=true for the employer's own structured facts. include_basic_organization_details and include_beta are accepted and add nothing.
  • Always null: organization_url, organization_logo, domain_derived, counties_derived, timezones_derived, location_requirements.
  • Values: employment_type uses FULL_TIME-style codes; source uses our system names (lever rather than lever.co; the old names are accepted as filters); timestamps end in Z.
  • Locations: the same City, Region, Country form; codes after a city (Toronto, ON) are also accepted.
  • Errors are the same application/problem+json shape, and unknown parameters are rejected with a suggestion.
  • Usage headers are named x-jobs-* and x-requests-*; see Errors, limits & usage.

Ids are different from Fantastic's: re-key your stored jobs with a backfill rather than mixing the two.