Ashby Salary Scraper - Startup Job Pay Ranges
Pricing
Pay per event
Go to Apify Store
Ashby Salary Scraper - Startup Job Pay Ranges
Ashby job postings with normalized annual salary ranges, equity flags and new-since-last-run detection.
Ashby Salary Scraper - Startup Job Pay Ranges
Pricing
Pay per event
Ashby job postings with normalized annual salary ranges, equity flags and new-since-last-run detection.
Ashby job board names or URLs, one per company. The name is the last part of the careers URL: jobs.ashbyhq.com/ramp means the name is ramp; names with spaces work too (jobs.ashbyhq.com/the%20browser%20company or the browser company). Boards that do not exist and entries that are not a board name or an Ashby link are skipped and listed in the run status; if none of the boards can be read, the run fails.
[ "ramp"]Optional. Keep a posting when its job title contains any of these words (case-insensitive), for example engineer or designer. Leave empty for all roles.
[]Optional. Keep only postings whose department contains one of these words (case-insensitive), for example Engineering or Sales. Companies name departments differently (OpenAI files sales roles under Go To Market), so check the department column of a first run.
[]Optional. Keep only postings whose team, the level below the department, contains one of these words (case-insensitive), for example Backend or Sales. Combined with departments, both must match.
[]Optional. Keep only postings whose primary or secondary locations, country, region or city contain one of these as a whole word or phrase, for example London, Germany or US (US matches Remote (US) but not Australia). Countries appear as the employer writes them, for example USA or United States.
[]Keep only fully remote postings: workplace type Remote. Hybrid and on-site roles are excluded even though Ashby flags Hybrid roles as isRemote. When the employer did not set a workplace type, the isRemote flag decides, and without it the word remote in the primary location.
Skip postings that do not show a salary range. Employers in some regions must publish pay, so this is a quick way to build a pay dataset.
Keep only postings whose top salary, converted to a yearly amount, reaches this value in the currency of the headline range (salaryCurrency). 0 disables the filter. Monthly, weekly, daily and hourly pay is annualised (12, 52, 260 and 2080 periods). Currencies are not converted, so combine it with the currency filter.
Optional. Keep only postings whose headline salary range (salaryMin/salaryMax, output field salaryCurrency) is in one of these currencies, as three-letter codes such as USD, GBP or EUR. A posting with a USD headline and an extra Canadian pay tier counts as USD; all tier currencies are listed in payTierCurrencies.
[]Keep only postings published at most N x 24 hours before the run. 0 disables the filter.
Return only postings this Actor has not already delivered to you for the same company and the same filters. The memory is kept in a storage on your account, separately for every company and every combination of filters (and state key), and only postings actually returned in a run are remembered, so postings cut off by the result limit or excluded by other filters come back later. The first run returns everything that matches.
Optional name for the only-new memory. Two schedules with the same filters share one memory; give each a different state key (for example team-a and team-b) when each of them must receive every new posting.
Adds the plain-text job description, cut to 8000 characters. Off by default to keep the dataset small.
Stop after this many postings in total across all companies.