SimplyHired Job Search & Salary Parser: MCP config, n8n workflow and API
SimplyHired job records from 23 country sites with parsed salary ranges, employment types, remote-work status, coordinates, full descriptions and application links.
Fastest route, in Claude Code:
claude mcp add --transport http simplyhired-job-search-and-salary-parser "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/simplyhired-job-search-and-salary-parser" One click, signs in with Apify on first use:
Any other client, one command (writes the config for 25+ agents, including Windsurf, Zed, Cline and Goose):
npx add-mcp "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/simplyhired-job-search-and-salary-parser" --name simplyhired-job-search-and-salary-parser Every file on this page is generated from the Actor's published schema: 51 of 51 checks pass (validated, not run)
- MCP configs: 7 of 7 (Uses Apify's hosted MCP endpoint over HTTPS; The tools parameter lists exactly the chosen Actors as owner/name; JSON configs parse and use the client's top-level key and the same URL; Codex TOML has a [mcp_servers.<name>] table with url and bearer_token_env_var; CLI commands quote the same URL and use the streamable HTTP transport; One-click install links decode back to the same URL and carry no token; Only placeholders, no real token)
- n8n workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
- long-run workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
- example input: 5 of 5 (All 1 required input field is present; Every input key exists in the published input schema; Every value has the type the schema declares; Every choice field uses one of its published options; Numbers respect the published minimum and maximum)
- code snippets: 4 of 4 (curl calls the documented run-sync-get-dataset-items endpoint for this Actor; Python (apify-client 3.x typed Run) and JavaScript use the official apify-client call() then read the run's dataset; Multi-line shell commands continue every line with a backslash; Token read from APIFY_TOKEN, none embedded)
- SKILL.md: 13 of 13 (SKILL.md starts with YAML front matter; name is 1-64 lowercase letters, digits and single hyphens; name matches the skill folder name; description is present, at most 1024 characters and has no angle brackets; front matter uses only spec fields; compatibility is at most 500 characters; body has instructions; field descriptions end on whole sentences; no credential values are embedded; the token is read from APIFY_TOKEN; the run command calls this Actor's run-sync endpoint; the example input is valid JSON; the example input matches the published input schema)
What a run costs
Every run pays a start fee plus a price per result. On the Free plan this Actor's start fee is $0.40 (the start event, $0.10 per GB, times its default 4 GB of memory), $0.12 on Business; results cost $0.99 per 1,000 results (pay per event). Checked 2026-11-12.
| Results in one run | Start | Results | Run total |
|---|---|---|---|
| 10 | $0.40 | $0.010 | $0.41 |
| 100 | $0.40 | $0.10 | $0.50 |
| 1,000 | $0.40 | $0.99 | $1.39 |
Plus Apify platform usage for the run, which the caller pays. A smaller memory setting lowers the start fee if the Actor still finishes. Prices can change; the Store pricing tab is the source of truth.
MCP config
One URL works in every client: https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/simplyhired-job-search-and-salary-parser. It exposes this Actor as a tool, plus fetch-actor-details so the agent can read the input schema before calling it. Pick your client:
Claude Code configterminal or .mcp.json
claude mcp add --transport http simplyhired-job-search-and-salary-parser "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/simplyhired-job-search-and-salary-parser" Run the command in your project folder. Add --scope user to make it available in every project. Full Claude Code setup
Claude Desktop configclaude_desktop_config.json
{
"mcpServers": {
"simplyhired-job-search-and-salary-parser": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--tools",
"fetch-actor-details,dataspryva/simplyhired-job-search-and-salary-parser"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN"
}
}
}
} Easiest: open Customize, then Connectors, choose Add custom connector, paste the server URL (the ChatGPT tab shows it on its own) and sign in to Apify. Full Claude Desktop setup
Cursor config~/.cursor/mcp.json
{
"mcpServers": {
"simplyhired-job-search-and-salary-parser": {
"url": "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/simplyhired-job-search-and-salary-parser",
"headers": {
"Authorization": "Bearer ${env:APIFY_TOKEN}"
}
}
}
} Save as ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one project. Merge with servers you already have. Full Cursor setup
VS Code config.vscode/mcp.json
{
"inputs": [
{
"type": "promptString",
"id": "apify-token",
"description": "Apify API token",
"password": true
}
],
"servers": {
"simplyhired-job-search-and-salary-parser": {
"type": "http",
"url": "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/simplyhired-job-search-and-salary-parser",
"headers": {
"Authorization": "Bearer ${input:apify-token}"
}
}
}
} Save as .vscode/mcp.json in your workspace. Full VS Code setup
ChatGPT configPlugins > Add custom MCP server
https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/simplyhired-job-search-and-salary-parser In ChatGPT on the web, open Plugins, select + and choose Add custom MCP server. Full ChatGPT setup
Codex CLI config~/.codex/config.toml
[mcp_servers.simplyhired-job-search-and-salary-parser]
url = "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/simplyhired-job-search-and-salary-parser"
bearer_token_env_var = "APIFY_TOKEN" Add the block to ~/.codex/config.toml, or .codex/config.toml in a project. Full Codex CLI setup
Gemini CLI configterminal (writes ~/.gemini/settings.json)
gemini mcp add -t http -s user -H "Authorization: Bearer $APIFY_TOKEN" simplyhired-job-search-and-salary-parser "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/simplyhired-job-search-and-salary-parser" Export APIFY_TOKEN first: the shell expands it and Gemini CLI saves the header, token included, in plain text in ~/.gemini/settings.json (keep that file private). In PowerShell write $env:APIFY_TOKEN instead of $APIFY_TOKEN. Drop -s user to save it in the project's .gemini/settings.json. Full Gemini CLI setup
n8n AI Agent configMCP Client Tool node
https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/simplyhired-job-search-and-salary-parser Add an AI Agent node, then attach an MCP Client Tool node to its tool input. Full n8n AI Agent setup
Tools your agent gets
Listed by Apify's MCP server 0.21.5 for this exact URL on 2026-11-11 (a tools/list call; nothing was run).
fetch-actor-detailsreads the input schemaget-actor-runchecks a run's statusget-dataset-itemsreads a run's resultsget-key-value-store-recordreads a stored record such as a file or summaryabort-actor-runstops a run that is still goingdataspryva--simplyhired-job-search-and-salary-parserruns the Actor and returns its results
n8n workflow
A manual and a daily trigger call the Actor through the HTTP Request node with your Apify token, then hand each record to the destination you pick. The Actor input sits in the request body, already filled with the example below.
- Run by hand
- Every day
- Run Apify Actor
n8n workflowsimplyhired-job-search-and-salary-parser.n8n.json
{
"name": "SimplyHired Job Search & Salary Parser to n8n only",
"nodes": [
{
"id": "49d4d386-8043-4beb-a12e-4d5eb198efd3",
"name": "Run by hand",
"type": "n8n-nodes-base.manualTrigger",
"typeVersion": 1,
"position": [
0,
0
],
"parameters": {}
},
{
"id": "6887fb66-a89c-4db1-aa49-2bc08b9bb2c3",
"name": "Every day",
"type": "n8n-nodes-base.scheduleTrigger",
"typeVersion": 1.2,
"position": [
0,
200
],
"parameters": {
"rule": {
"interval": [
{
"triggerAtHour": 8
}
]
}
},
"notes": "Activate the workflow to run on this schedule."
},
{
"id": "6c689c3a-71c7-4036-a9b3-2bfba3c5989f",
"name": "Run Apify Actor",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.2,
"position": [
260,
100
],
"parameters": {
"method": "POST",
"url": "https://api.apify.com/v2/actors/dataspryva~simplyhired-job-search-and-salary-parser/run-sync-get-dataset-items",
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"sendBody": true,
"specifyBody": "json",
"jsonBody": "{\n \"mode\": \"search\",\n \"searchQueries\": [\n \"software engineer\"\n ],\n \"location\": \"New York\",\n \"country\": \"united-states\",\n \"sortBy\": \"relevance\",\n \"minSalary\": 0,\n \"fetchJobDetails\": true,\n \"enrichCompanyPages\": false,\n \"maximizeCoverage\": false,\n \"maxItems\": 3\n}",
"options": {
"timeout": 310000
}
},
"notes": "Actor: dataspryva/simplyhired-job-search-and-salary-parser. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.",
"notesInFlow": false
},
{
"id": "e573f876-6d22-4bed-ab7b-48b06ae6384b",
"name": "Setup",
"type": "n8n-nodes-base.stickyNote",
"typeVersion": 1,
"position": [
0,
-370
],
"parameters": {
"content": "## SimplyHired Job Search & Salary Parser\n\nSource: [dataspryva/simplyhired-job-search-and-salary-parser](https://apify.com/dataspryva/simplyhired-job-search-and-salary-parser) on Apify.\n\n1. In **Run Apify Actor**, create a Header Auth credential: name `Authorization`, value `Bearer YOUR_APIFY_TOKEN` with your token.\n2. Click **Execute workflow**. Each record arrives as one n8n item.\n3. Edit the JSON body of **Run Apify Actor** to change the input.\n\nGenerated by recipeforagents.com. Validated, not executed: runs are billed to your Apify account.",
"height": 340,
"width": 460,
"color": 6
}
}
],
"connections": {
"Run by hand": {
"main": [
[
{
"node": "Run Apify Actor",
"type": "main",
"index": 0
}
]
]
},
"Every day": {
"main": [
[
{
"node": "Run Apify Actor",
"type": "main",
"index": 0
}
]
]
}
},
"pinData": {},
"active": false,
"settings": {
"executionOrder": "v1"
},
"meta": {
"templateCredsSetupCompleted": false
},
"tags": []
} Import with Workflows, Import from file, or paste into the canvas. Credentials are not included: you select them after import.
All 7 destination variants pass the same checks at build time. Built-in nodes only, at versions n8n has shipped since 1.80: they import on n8n Cloud and older self-hosted instances without community nodes. Prefer Apify's own node? The verified community node @apify/n8n-nodes-apify runs the same Actor with OAuth sign-in on n8n Cloud.
Runs longer than 5 minutes? The synchronous endpoint answers HTTP 408 after 300 seconds. The long-run variant starts the run, checks it every minute until it ends, then reads its dataset (HTTP Request, If and Stop and Error nodes only).
Download the long-run workflow11 of 11 checks pass, not executed
Call it from code
Run the Actor from a script or your own agent framework with the Apify API. The call waits for the run to finish and returns the records. The input is the example below.
curl
curl -X POST "https://api.apify.com/v2/actors/dataspryva~simplyhired-job-search-and-salary-parser/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"mode":"search","searchQueries":["software engineer"],"location":"New York","country":"united-states","sortBy":"relevance","minSalary":0,"fetchJobDetails":true,"enrichCompanyPages":false,"maximizeCoverage":false,"maxItems":3}' Install: pip install "apify-client>=3"
Python
import os
from apify_client import ApifyClient
client = ApifyClient(os.environ["APIFY_TOKEN"])
run_input = {
"mode": "search",
"searchQueries": [
"software engineer",
],
"location": "New York",
"country": "united-states",
"sortBy": "relevance",
"minSalary": 0,
"fetchJobDetails": True,
"enrichCompanyPages": False,
"maximizeCoverage": False,
"maxItems": 3,
}
run = client.actor("dataspryva/simplyhired-job-search-and-salary-parser").call(run_input=run_input)
if run is None:
raise RuntimeError("The Actor run could not be started")
print(run.status, "dataset", run.default_dataset_id)
for item in client.dataset(run.default_dataset_id).iterate_items():
print(item) Install: npm install apify-client
JavaScript
import { ApifyClient } from "apify-client";
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const input = {
"mode": "search",
"searchQueries": [
"software engineer"
],
"location": "New York",
"country": "united-states",
"sortBy": "relevance",
"minSalary": 0,
"fetchJobDetails": true,
"enrichCompanyPages": false,
"maximizeCoverage": false,
"maxItems": 3
};
const run = await client.actor("dataspryva/simplyhired-job-search-and-salary-parser").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.length, items[0]); Example input
These values come from the Actor's Store prefill and required defaults. Change the search, URL or limit before your first run.
Actor inputinput.json
{
"mode": "search",
"searchQueries": [
"software engineer"
],
"location": "New York",
"country": "united-states",
"sortBy": "relevance",
"minSalary": 0,
"fetchJobDetails": true,
"enrichCompanyPages": false,
"maximizeCoverage": false,
"maxItems": 3
} | Field | Type | What it does |
|---|---|---|
mode required | string (2 options) | What to fetch: search jobs on SimplyHired, or scrape specific SimplyHired URLs you already have. |
searchQueries | array | One or more job titles, skills, or keywords. Each entry runs as its own search, e.g. registered nurse or python developer, remote. Ignored when Search URLs are provided. |
searchUrls | array | Full SimplyHired search URLs, including any filters and a country domain (e.g. https://www.simplyhired.co.uk/search?q=nurse&l=London). When provided, these are used instead of the query, location and filter fields. |
jobUrls | array | SimplyHired job URLs (https://www.simplyhired.com/job/...) or search URLs to scrape directly. Job IDs may also be pasted on their own. |
location | string | City, state, ZIP code, or remote. Leave empty to search nationwide (mode=search). |
country | string (23 options) | Which SimplyHired site to search (mode=search). Choose the country that matches your location. |
radius | string (8 options) | Distance around the location (mode=search). Only applies when a location is set. |
sortBy | string (3 options) | Order of the search results (mode=search). |
datePosted | string (6 options) | Only include jobs added within this window (mode=search). |
employmentType | string (9 options) | Filter by employment type (mode=search). |
minSalary | integer | Only jobs with pay at or above this amount, in the local currency of the selected country (e.g. 100000 = $100,000 a year on the US site). Leave 0 for no filter. |
remoteType | string (3 options) | Filter by remote work arrangement (mode=search). |
developerSkill | string (22 options) | Only jobs tagged with this software skill (mode=search). Applies mainly to tech roles; combine several skills with Developer skills below. |
developerSkills | array | Additional software skills to require together with the Developer skill above (mode=search). Use skill names such as Python, SQL, React (or their codes). Jobs must match every listed skill. |
fetchJobDetails | boolean | Fetch each job's detail payload for the full description, parsed salary, coordinates, qualifications and employer rating. Adds one fast request per job. Turn off for search-card fields only. |
enrichCompanyPages | boolean | Look up each employer's SimplyHired company page (once per employer) and add its address, size, revenue band and industry when the page's company name matches the listing. Off by default. |
maximizeCoverage | boolean | When a search hits SimplyHired's per-search result limit, continue with extra facet searches (job types and developer skills) and merge the unique jobs. Slower and uses more requests, but returns more of the matching… |
maxItems | integer | Hard cap on the number of job records returned. |
What your agent receives
Each run returns a list of records. The Actor publishes 11 fields, starting with title, company, location, salary.
| Field |
|---|
title |
company |
location |
salary |
salaryMin |
salaryMax |
salaryCurrency |
employmentType |
remoteType |
datePosted |
1 more fields
| Field |
|---|
jobUrl |
Agent skill
A SKILL.md in the open Agent Skills format. It teaches Claude Code, Codex and other skill-aware agents when to call this Actor, how to build the input and how to read the result, using the API directly.
SKILL.mdsimplyhired-job-search-and-salary-parser/SKILL.md
---
name: simplyhired-job-search-and-salary-parser
description: "SimplyHired job records from 23 country sites with parsed salary ranges, employment types, remote-work status, coordinates, full descriptions and application links. Runs the Apify Actor dataspryva/simplyhired-job-search-and-salary-parser. Use when the user needs SimplyHired data with fields such as title, company, location, salary, salaryMin, salaryMax and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
actor: "dataspryva/simplyhired-job-search-and-salary-parser"
store-url: "https://apify.com/dataspryva/simplyhired-job-search-and-salary-parser"
---
# SimplyHired Job Search & Salary Parser
Use this skill to fetch SimplyHired data with the Apify Actor `dataspryva/simplyhired-job-search-and-salary-parser` and work with the returned rows.
## Before running
1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.
## Input fields
| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | one of `search`, `byUrl`, required | What to fetch: search jobs on SimplyHired, or scrape specific SimplyHired URLs you already have. |
| `searchQueries` | array | One or more job titles, skills, or keywords. Each entry runs as its own search, e.g. `registered nurse` or `python developer, remote`. Ignored when Search URLs are provided. |
| `searchUrls` | array | Full SimplyHired search URLs, including any filters and a country domain (e.g. https://www.simplyhired.co.uk/search?q=nurse&l=London). When provided, these are used instead of the query, location and filter fields. |
| `jobUrls` | array | SimplyHired job URLs (https://www.simplyhired.com/job/...) or search URLs to scrape directly. Job IDs may also be pasted on their own. |
| `location` | string | City, state, ZIP code, or `remote`. Leave empty to search nationwide (mode=search). |
| `country` | string | Which SimplyHired site to search (mode=search). Choose the country that matches your location. |
| `radius` | one of `exact`, `5`, `10`, `15`, `25`, `50`, `100` | Distance around the location (mode=search). Only applies when a location is set. |
| `sortBy` | one of `relevance`, `date`, `distance` | Order of the search results (mode=search). |
| `datePosted` | one of `1`, `3`, `7`, `14`, `30` | Only include jobs added within this window (mode=search). |
| `employmentType` | string | Filter by employment type (mode=search). |
| `minSalary` | integer | Only jobs with pay at or above this amount, in the local currency of the selected country (e.g. 100000 = $100,000 a year on the US site). Leave 0 for no filter. |
| `remoteType` | one of `Remote`, `Hybrid work` | Filter by remote work arrangement (mode=search). |
| `developerSkill` | string | Only jobs tagged with this software skill (mode=search). Applies mainly to tech roles; combine several skills with Developer skills below. |
| `developerSkills` | array | Additional software skills to require together with the Developer skill above (mode=search). Use skill names such as `Python`, `SQL`, `React` (or their codes). Jobs must match every listed skill. |
Example `input.json` (the Actor's published prefill):
```json
{
"mode": "search",
"searchQueries": [
"software engineer"
],
"location": "New York",
"country": "united-states",
"sortBy": "relevance",
"minSalary": 0,
"fetchJobDetails": true,
"enrichCompanyPages": false,
"maximizeCoverage": false,
"maxItems": 3
}
```
## Run
```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~simplyhired-job-search-and-salary-parser/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d @input.json > results.json
```
The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/dataspryva~simplyhired-job-search-and-salary-parser/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.
## Output
Each item is one record. Published fields include: `title`, `company`, `location`, `salary`, `salaryMin`, `salaryMax`, `salaryCurrency`, `employmentType`, `remoteType`, `datePosted`, `jobUrl`.
Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.
- Claude Code: save it as
~/.claude/skills/simplyhired-job-search-and-salary-parser/SKILL.md, or.claude/skills/simplyhired-job-search-and-salary-parser/SKILL.mdin a project. - Codex and other agents:
~/.agents/skills/simplyhired-job-search-and-salary-parser/SKILL.md, or.agents/skills/simplyhired-job-search-and-salary-parser/in a project. - Or let the skills CLI place it for your agent:
npx skills add https://recipeforagents.com --skill simplyhired-job-search-and-salary-parser - Set
APIFY_TOKENin the agent's environment.
Troubleshooting
Why does the client say Unauthorized or invalid token?
Every Apify Actor tool needs a signed-in Apify account. Reconnect the server so the OAuth sign-in runs again, or switch to the token variant: an Authorization: Bearer header with an API token from Apify Console, Settings, API and integrations. For a local server the token must be in the server's own env block, not only in your shell.
Source: Apify MCP server README
Why did my agent's tool list change after an update?
Without a tools parameter Apify's server loads its default tool set, which changes between releases. The URLs on this site pin the tools with ?tools=, so the agent always gets the same Actor tool plus fetch-actor-details. Apify's README gives the same advice for production.
Source: Apify MCP server README
What happens when the agent sends input the Actor rejects?
The server answers with the Actor's input schema, so the agent can fix the arguments and call again. The fetch-actor-details tool in every scoped URL lets it read that schema before the first call.
Source: Apify MCP server README
Questions
How do I connect SimplyHired Job Search & Salary Parser to Claude?
In Claude Code run: claude mcp add --transport http simplyhired-job-search-and-salary-parser "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/simplyhired-job-search-and-salary-parser". In Claude Desktop or claude.ai add a custom connector with the URL https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/simplyhired-job-search-and-salary-parser and sign in to Apify. The agent then gets one tool for this Actor plus a tool that reads its input schema.
What input does SimplyHired Job Search & Salary Parser need?
The published input schema requires mode. The example on this page uses the Actor's own Store prefill.
What does SimplyHired Job Search & Salary Parser cost to run?
The Apify Store lists $0.99 per 1,000 results (pay per event) for this Actor, checked 2026-11-12. Runs are billed to the Apify account whose token or sign-in the agent uses; Apify platform usage can add to that.
Which tools does the MCP config give my agent?
6 tools: fetch-actor-details, get-actor-run, get-dataset-items, get-key-value-store-record, abort-actor-run, dataspryva--simplyhired-job-search-and-salary-parser. Apify's MCP server listed them for this exact URL on 2026-11-11.
More SimplyHired Actors
Fiverr Gig & Seller Sitemap Directory Scraper
List live Fiverr gigs, seller profiles, categories, search tags and Logo Maker ideas straight from Fiverr's…
14 fields$0.99 per 1,000 resultsGulfTalent Job Listings Across 16 Middle East Markets
Search GulfTalent by keyword, category, industry, job type or nationality preference, or browse one…
12 fields$0.99 per 1,000 results99designs Designer Portfolio & Stats Finder
Browse 99designs designer profiles by keyword and category, or fetch specific designers by URL or ID, with…
9 fields$0.99 per 1,000 resultsAshby Job Board Compensation & Openings Scraper
Scrape public Ashby job boards for any company hiring on jobs.ashbyhq.com. Get every open role with title…
7 fields$0.99 per 1,000 resultsBayt.com MENA Job Listing & Salary Scraper
Search Bayt.com job listings across Middle East and North Africa countries by keyword, location, career…
0 fields$0.99 per 1,000 resultsBuiltIn Tech Company Directory & Hiring Signal Scraper
Browse BuiltIn.com's US tech-company directory across multiple cities by industry, technology, size and work…
13 fields$0.99 per 1,000 results