Ashby Jobs Scraper — New Postings Since Any Date
Ashby job-board API postings published since a supplied date or window, with job metadata, URLs, timestamps and optional descriptions.
Open Ashby Jobs on Apify →The one question it answers
Which roles did these companies post on Ashby since my last run?
Input
| Field | What to put | Default |
|---|---|---|
companies | Ashby board names or full board URLs such as https://jobs.ashbyhq.com/<name> | required |
since | 24h, 7d, 2w, or an ISO date/time | empty |
maxResults | Cap across companies, newest first | 500 |
includeDescription | Add the plain-text description to each posting | false |
Identifiers can be pasted as full URLs; the Actor extracts the slug.
Output
One dataset item per posting:
ats company job_id title url apply_url published_at updated_at location locations[] workplace_type department team employment_type compensation description source_url fetched_at run_sinceFields the board does not state are null — nothing is inferred from text. source_url is the exact API URL each record came from.
How it works
- Reads the company's public Ashby job-board API directly. No login, no proxies, and no HTML-page scraping.
sinceis applied to the posting'spublishedAttimestamp. Timestamps are returned in UTC ISO-8601.- Runs are stateless and suitable for a daily delta with
since: 24h. - Rate limits and upstream errors are retried with backoff; per-company statuses and counts are reported.
Pricing
Pay per result: a small run start fee plus a fee per posting returned. Postings are charged only when delivered; errors, empty boards, and unknown identifiers cost nothing beyond the start fee. Set Max total charge to cap spend.
Limits
- Public boards only — private or internal postings are not available from the API.
- Up to 1,000 identifiers per run and up to 100,000 results.
- If every identifier fails, the run fails rather than silently returning nothing.
Attribution
Data from the company's public Ashby job-board API. This Actor is not affiliated with Ashby.