India + ATS Career Site Jobs API

Search 6,801 company career sites across 24 ATS platforms — Greenhouse, Lever, Ashby, Workday, Zoho Recruit, Keka, RippleHire, and more.

Built for India IT services coverage (HCL, Infosys, Wipro, Accenture, Capgemini, Zoho) that most US-based job APIs don't track. Direct employer apply URLs, not aggregator redirects. Not LinkedIn, Indeed, or Naukri.

This is a nightly-refreshed index, not a live scrape per run. Every row carries lastSeenAt — the last time the refresh confirmed that posting was still on the employer's own board, not a one-time snapshot.

Quick start

Default input (cheap, fast — a few seconds, ~25 results):

{
  "keywords": "software engineer",
  "countries": ["India"],
  "postedWithinDays": 7,
  "maxItems": 25
}

Incremental / only-new (for a scheduled recurring run):

{
  "keywords": "software engineer",
  "countries": ["India"],
  "postedAfter": "2026-10-01",
  "maxItems": 100
}

You're billed per matched job actually returned, not for the size of the underlying index.

Coverage (measured 2026-10-02)

Active jobs	310,357
Companies	6,801
Sources	24 ATS / career-site feeds
Refresh	Nightly — lastSeenAt on every row

Single-employer feeds (not multi-tenant ATS platforms): Amazon, Netflix, Accenture, HCLTech, and similar — filter with ats or company.

Input

Field	What it does
keywords	Comma-separated search terms, matched against title + company (full-text, prefix-matched — "engineer" matches "Engineering")
countries	Country names; aliases accepted (usa, uk, uae)
city	City names; common spelling variants normalized
workModes	remote, hybrid, onsite
ats	Source filter — most are multi-tenant ATS platforms, a few are single-employer feeds
company	Exact company name(s)
postedWithinDays	Relative freshness window
postedAfter	YYYY-MM-DD — use for scheduled, only-new runs
maxItems	Cap on returned rows. Default 25, kept low so a first run is cheap

Sample output

{
  "id": "64698bc76e34a0db32dbf6f9c3affa24",
  "title": "Product Security Engineer, Senior",
  "company": "TraceLink, Inc",
  "companyDomain": "tracelink.com",
  "applyUrl": "https://www.tracelink.com/about/culture-and-careers/jobs?gh_jid=5244088007",
  "ats": "greenhouse",
  "city": "Pune",
  "country": "India",
  "isRemote": false,
  "postedAt": "2026-10-02",
  "lastSeenAt": "2026-10-02T14:04:22.434Z"
}

id is a stable hash of applyUrl — use it as the dedup key across separate runs.

What this is for

• India / IT-services sourcing that needs HCL, Infosys, Wipro, Accenture, Capgemini coverage straight from the career site, not Naukri
• A filtered career-site feed for a newsletter or job board
• Recruiter watchlists — one query instead of visiting 50 separate career pages

Limitations

• No job descriptions in v1 — not stored. Title, location, apply URL, and dates only.
• Not live. The index refreshes roughly every 24 hours. If the freshest result in a run is older than ~36h, the Actor logs a warning rather than serving stale data silently.
• Not LinkedIn, Indeed, or Naukri. Employer career pages only. applyUrl reflects the source as of the last refresh; closed listings are dropped automatically.
• experienceMin is almost never filled — only 2 of 24 sources publish structured years-of-experience data. It's included in the output when present, not offered as a filter.
• Field completeness (measured 2026-10-02): city 32% null (78% on remote postings specifically), country 22%, companyDomain 24%, postedAt 8%.
• Volume skews toward a few large employers (Accenture, RippleHire, HCLTech). Use company/ats if you want to exclude that mix.
• ~0.07% of rows can be the same real opening listed on two different sources — not cross-deduplicated.
• One aggregator source with tracking-redirect URLs (not the employer's own link) is excluded entirely.

Notes

This Actor has no scraper of its own — it queries a backend index built from each source's public job board, refreshed nightly.