CSV integration

A feed is an API endpoint for a company's job board on an ATS. Our catalog includes account slug, feed URL, platform, and lifecycle metadata. It is not a job posting and not a normalized job record.

Store feeds as your own copy in your database. You work from that local catalog when fetching jobs and scheduling syncs.

Download a catalog snapshot, a point-in-time CSV file, and import it into your infrastructure. Good for a one-time seed without an API subscription. Same fields as the API, without pagination or incremental sync.

Want to explore the schema first? Download a free sample with real feeds from every supported ATS platform — no signup required.

Job data lives on each company's ATS, not in the ATS Feeds catalog. For each feed in your workflow, HTTP GET the feed_url and parse the response into your job store.

Response shape is platform-specific. Greenhouse, Lever, Ashby, and others each expose their own JSON. Plan one fetch worker and one parser per ATS you support.

ATS Feeds does not normalize or enrich postings. You own storage, deduplication, search indexing, and refresh scheduling for the jobs you pull.

Companys launch and retire job boards over time. Your local feed catalog needs to reflect new boards and drop retired ones on whatever cadence fits your product.

Download a fresh catalog snapshot and replace your local copy manually. This can be cheaper if you only need to refresh once a month, but there is no automation. You run the import yourself each time.