Ashby Companies and Jobs, as Structured Rows
Find companies using Ashby, check a prospect list, or retrieve their job postings with employer-published salary data. Choose the output mode for the requested result.
When to use this skill
- Someone wants Ashby jobs and does not want to read jobs.ashbyhq.com boards by hand.
- You are filling a job board, a market-intel dashboard, or a sourcing tool with roles from Ashby-hosted careers pages.
- You need salary as numbers the employer actually published, not a string a human has to read or a model has to guess.
- You went looking for an Ashby jobs API and found only the employer-side APIs you cannot sign up for.
- Someone asks which companies use Ashby, wants an ATS market map, or needs to check a prospect list for Ashby boards.
- You need live open-role counts before choosing which boards to feed into a jobs pipeline.
Choose outputMode for the question: jobs for postings, companiesOnly for company discovery or verification, and urlsOnly for a cheap board index. See references/actor-index.md.
What you get
In jobs mode, one dataset row per job. resultType separates job rows from error rows.
Core fields:
id, url (canonical, safe as a dedupe key), applyUrl, title
companyName, boardToken, boardUrl
department, team, departments, employmentType, workplaceType, isRemote
location, secondaryLocations, locationsDerived, countriesDerived, address
datePublished, isListed
compensationSummary (the employer's own pay line), salaryRaw (structured, verbatim), salaryDerived, and flat salaryMin, salaryMax, salaryCurrency, salaryPeriod, salaryTiers, offersEquity
descriptionMarkdown (default add-on), descriptionHtml, descriptionText (opt-in add-ons)
source (always ashby), sourceType, scrapedAt
With includeCompanyData on, each row also carries companyWebsite, companyLogo, remoteEligibility (the countries remote applicants may live in, as the employer declared them), applicationDeadline, and directApply.
The Actor ships dataset views for the console: overview, salaries (sortable pay columns), companies, and newPostings.
Company rows
With outputMode: "companiesOnly", the dataset has one row per company. resultType separates company rows from error rows.
companyName, boardToken, boardUrl
jobCount: live open roles at verification time
live: whether the board answered the probe (null when verification is off)
verifiedAt, scrapedAt
A failed prospect check returns an error row with errorCode: board_not_found, errorMessage, and optional didYouMean suggestions. The companies dataset view presents company name, slug, open jobs, live flag, and board link.
Prerequisites
The Actor
Run it with the Apify CLI
Engineering roles from two boards, capped at 25:
apify actors call "johnvc/ashby-job-board-scraper" -i '{"companies":["cerebras","ramp"],"titleKeywords":["engineer"],"maxJobs":25}' \
--json \
--user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
2>/dev/null
Remote full-time roles with pay, descriptions off for cheaper metadata rows:
apify actors call "johnvc/ashby-job-board-scraper" -i '{"companies":["openai","ramp","deel"],"remoteOnly":true,"employmentTypes":["FullTime"],"includeDescriptionMarkdown":false,"maxJobs":100}' \
--json \
--user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
2>/dev/null
Only postings added in the last day, the shape to put on a daily schedule:
apify actors call "johnvc/ashby-job-board-scraper" -i '{"companies":["openai","notion","linear"],"publishedAfter":"25h","maxJobs":200}' \
--json \
--user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
2>/dev/null
Confirm the live schema and prices before a large batch:
apify actors info "johnvc/ashby-job-board-scraper" --json \
--user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
2>/dev/null
Read the rows back from a finished run:
apify datasets get-items <DATASET_ID> --format json \
--user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
2>/dev/null
Discover up to 100 Ashby boards from the directory and verify them live:
apify actors call "johnvc/ashby-job-board-scraper" -i '{"outputMode":"companiesOnly","maxCompanies":100}' \
--json \
--user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
2>/dev/null
Check a prospect list, including explicit misses:
apify actors call "johnvc/ashby-job-board-scraper" -i '{"companies":["Black Semiconductor","Morse Micro","Ramp","Notarealcompany Xyz"],"outputMode":"companiesOnly"}' \
--json \
--user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
2>/dev/null
Every call carries the three flags this repo expects: --json (or --format json), --user-agent apify-awesome-skills/apify-ashby-jobs-scraper, and 2>/dev/null.
Run it from Claude or another AI agent (MCP)
The Actor is MCP-ready. Add the hosted server URL:
https://mcp.apify.com/?tools=actors,docs,johnvc/ashby-job-board-scraper
Then ask, for example: "Pull the remote engineering jobs from OpenAI and Ramp with published salary ranges, and rank them by salaryMax." MCP setup docs: https://docs.apify.com/platform/integrations/mcp
Workflow: job postings
- Start with one or two boards and
maxJobs around 25. Look at the row shape before you pay for a wide crawl.
- Company names work as input. "Black Semiconductor" finds the blacksemiconductor board; the Actor tries slug spellings automatically and returns a
board_not_found error row on a miss, optionally with didYouMean suggestions.
- Filter at the source, not downstream.
titleKeywords, departments, locationKeywords, employmentTypes, remoteOnly, and publishedAfter all drop jobs before they are billed. For fully remote requests, also check workplaceType: remoteOnly can return Hybrid jobs.
- Keep
includeDescriptionMarkdown on for LLM pipelines; turn it off for metadata-only rows at roughly half the per-row cost.
- For salary work, read the flat columns and
salaryDerived.source. Published ranges can come from native compensation data or description parsing, even when shouldDisplayCompensation is false. Do not infer missing pay.
- Check
resultType before treating a row as a job. An error row carries errorCode and a human-readable errorMessage.
- Dedupe downstream on
url. It is canonical and survives a company editing the title.
Workflow: companies and prospect checks
- For directory discovery, select
outputMode: "companiesOnly", optionally narrow names and slugs with discoveryQuery, and cap the sweep with maxCompanies. For prospect checks, supply the requested names, slugs, or board URLs in companies.
- Keep
verifyCompanies on for current counts; distinguish company rows from errors. Sort verified rows by jobCount within the returned sample, not as a claim about every Ashby customer. A name match is not an industry classification.
- Deduplicate by
boardToken, since one company can operate multiple boards. Re-run when current counts are needed rather than presenting a cached directory snapshot as live.
Continue from companies to job postings
When the request includes retrieving their jobs, keep valid company rows and deduplicate their non-empty boardToken values. Pass those values as companies in a second call to the same Actor with explicit outputMode: "jobs", the user's filters, and a separate job cap. Stop when no valid tokens remain: an empty companies array triggers a directory sweep and would broaden the request.
Inputs
companies (array): company names, board slugs, or jobs.ashbyhq.com URLs (board, embed, or single job), mixed freely. Empty sweeps the bundled directory.
startUrls (array): the same values in URL-list form; merged with companies.
outputMode (enum jobs, urlsOnly, companiesOnly, default jobs)
titleKeywords, departments, locationKeywords (arrays): keep-only filters, run before billing.
employmentTypes (array of FullTime, PartTime, Intern, Contract, Temporary)
remoteOnly (boolean, default false)
publishedAfter (string): 24h, 7d, 2w, or an ISO date.
includeDescriptionMarkdown (boolean, default true), includeDescriptionHtml, includeDescriptionText (default false)
includeCompanyData (boolean, default false): job-page enrichment, one extra request per job.
report (enum none, markdown, html): a whole-run digest in the key-value store.
maxJobs (integer, default 100): the primary spend cap. maxJobsPerCompany, maxCompanies, maxConcurrency refine it.
proxyConfiguration (object): off by default; direct connections work.
Company-mode inputs:
outputMode: set companiesOnly for discovery or prospect verification.
companies (array): prospect names, slugs, or board URLs; omit it for a directory sweep.
discoveryQuery (string): case-insensitive text match over directory names and slugs.
verifyCompanies (boolean, default true): live-probe candidates; dead boards are skipped and not billed as company rows.
maxCompanies (integer, default 25): the primary cap for directory sweeps.
maxConcurrency (integer, default 5): parallel probes.
Cost
Billing is pay per event with no start fee, so a run that returns nothing costs almost nothing. Confirm live prices with the info command above rather than trusting a number copied here.
The base job-result event fires once per delivered job row, salary data included. Add-on events fire only on rows that carry the extra: job-description-markdown (on by default), job-description-html, job-description-text, job-company-data, and a flat run-report. Company discovery rows and URL index rows have their own cheaper events.
Jobs removed by your filters are never charged. As a shape, 100 jobs with Markdown descriptions is small change.
Suggested confirmation thresholds: mention the estimate under about $5, warn the user over about $5, get explicit confirmation over about $20. Present cost as "around $X", never as a guarantee.
Honest limits
- No update timestamps exist. Ashby publishes only
publishedAt, so publishedAfter gives you a new-postings feed; there is no changed-jobs feed and no field pretends otherwise.
- Salary appears only when the employer displays compensation on the posting. Nothing is inferred by a model;
salaryDerived.source tells you whether a value came from the structured data or a deterministic text parse.
- Public board data only. No applicant data, no recruiter contacts, nothing behind a login.
- One board is one request, so very large boards return in a single response; a board too large to process returns a clear in-band error rather than a partial dataset.
- The bundled directory can omit newly launched boards. Try a direct company or board-URL check when a directory search misses a known prospect.
- Company names come from the directory; a board outside it may use its slug as the name. One company may operate multiple board slugs, each returned as its own row.
- Public board presence shows that a company hires through Ashby; it does not establish contract value, seats, or tenure.
Troubleshooting
board_not_found: the slug does not exist on the public API. Check didYouMean if present on the error row, or paste the board URL instead of a name.
job_not_found: a single-job URL points at a posting that closed. Fetch the whole board instead.
http_error: the source answered abnormally; the row says which HTTP status. Retry once before assuming anything.
- Zero rows and no error row: your filters removed everything. Relax
publishedAfter or titleKeywords first.
- Duplicates across runs: dedupe on
url, never on title.
- Empty company sweep: loosen or remove
discoveryQuery.
jobCount and live are null: verifyCompanies was off, so the row is a directory snapshot rather than a live read.
See references/gotchas.md for cost guardrails and error recovery, and references/actor-index.md for the Actor routing table.
Related Actors
1---
2name: apify-ashby-jobs-scraper
3description: "Scrape Ashby jobs or discover companies using Ashby with the Apify Ashby Job Board API Actor (johnvc/ashby-job-board-scraper). Job mode returns live job rows with title, company, location, remote and employment fields, publish date, apply URL, employer-published salary columns, equity flag, and Markdown descriptions. Company mode finds Ashby boards from a bundled directory or checks a prospect list, returning company name, board slug and URL, live open-job count, and verification fields. Takes company names, board slugs, or board URLs; supports pre-billing job filters and publishedAfter feeds. Use for Ashby jobs data or API requests, salary and remote-role collection, job-board pipelines, companies using Ashby/Ashby customers, ATS market maps, prospect checks, and recruiting or sales target lists. Billed per delivered result with no start fee, and MCP-ready for Claude and other AI agents."
4author: John Cole
5author_url: https://github.com/johnisanerd
6license: MIT
7metadata:
8 source: https://skillmd.com/skills/apify/apify-ashby-jobs-scraper
9 version: "1.0"
10 keywords: "ashby, jobs, job-board, salary, remote-work, company-discovery, prospect-check"
11---
12
13# Ashby Companies and Jobs, as Structured Rows
14
15Find companies using Ashby, check a prospect list, or retrieve their job postings with employer-published salary data. Choose the output mode for the requested result.
16
17## When to use this skill
18
19- Someone wants Ashby jobs and does not want to read jobs.ashbyhq.com boards by hand.
20- You are filling a job board, a market-intel dashboard, or a sourcing tool with roles from Ashby-hosted careers pages.
21- You need salary as numbers the employer actually published, not a string a human has to read or a model has to guess.
22- You went looking for an Ashby jobs API and found only the employer-side APIs you cannot sign up for.
23- Someone asks which companies use Ashby, wants an ATS market map, or needs to check a prospect list for Ashby boards.
24- You need live open-role counts before choosing which boards to feed into a jobs pipeline.
25
26Choose `outputMode` for the question: `jobs` for postings, `companiesOnly` for company discovery or verification, and `urlsOnly` for a cheap board index. See `references/actor-index.md`.
27
28## What you get
29
30In `jobs` mode, one dataset row per job. `resultType` separates `job` rows from `error` rows.
31
32Core fields:
33
34- `id`, `url` (canonical, safe as a dedupe key), `applyUrl`, `title`
35- `companyName`, `boardToken`, `boardUrl`
36- `department`, `team`, `departments`, `employmentType`, `workplaceType`, `isRemote`
37- `location`, `secondaryLocations`, `locationsDerived`, `countriesDerived`, `address`
38- `datePublished`, `isListed`
39- `compensationSummary` (the employer's own pay line), `salaryRaw` (structured, verbatim), `salaryDerived`, and flat `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryPeriod`, `salaryTiers`, `offersEquity`
40- `descriptionMarkdown` (default add-on), `descriptionHtml`, `descriptionText` (opt-in add-ons)
41- `source` (always `ashby`), `sourceType`, `scrapedAt`
42
43With `includeCompanyData` on, each row also carries `companyWebsite`, `companyLogo`, `remoteEligibility` (the countries remote applicants may live in, as the employer declared them), `applicationDeadline`, and `directApply`.
44
45The Actor ships dataset views for the console: `overview`, `salaries` (sortable pay columns), `companies`, and `newPostings`.
46
47### Company rows
48
49With `outputMode: "companiesOnly"`, the dataset has one row per company. `resultType` separates `company` rows from `error` rows.
50
51- `companyName`, `boardToken`, `boardUrl`
52- `jobCount`: live open roles at verification time
53- `live`: whether the board answered the probe (`null` when verification is off)
54- `verifiedAt`, `scrapedAt`
55
56A failed prospect check returns an error row with `errorCode: board_not_found`, `errorMessage`, and optional `didYouMean` suggestions. The `companies` dataset view presents company name, slug, open jobs, live flag, and board link.
57
58## Prerequisites
59
60- Apify account (sign up at https://apify.com?fpr=9n7kx3&fp_sid=awesomeskills).
61- Authentication via `apify login`, or an `APIFY_TOKEN` environment variable (Apify Console, Settings, Integrations).
62
63## The Actor
64
65- Store page: https://apify.com/johnvc/ashby-job-board-scraper?fpr=9n7kx3&fp_sid=awesomeskills
66- Actor ID: `johnvc/ashby-job-board-scraper`
67- Pricing: pay per event, no start fee. See the cost section below and `references/gotchas.md` for the live-price command.
68
69## Run it with the Apify CLI
70
71Engineering roles from two boards, capped at 25:
72
73```bash
74apify actors call "johnvc/ashby-job-board-scraper" -i '{"companies":["cerebras","ramp"],"titleKeywords":["engineer"],"maxJobs":25}' \
75 --json \
76 --user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
77 2>/dev/null
78```
79
80Remote full-time roles with pay, descriptions off for cheaper metadata rows:
81
82```bash
83apify actors call "johnvc/ashby-job-board-scraper" -i '{"companies":["openai","ramp","deel"],"remoteOnly":true,"employmentTypes":["FullTime"],"includeDescriptionMarkdown":false,"maxJobs":100}' \
84 --json \
85 --user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
86 2>/dev/null
87```
88
89Only postings added in the last day, the shape to put on a daily schedule:
90
91```bash
92apify actors call "johnvc/ashby-job-board-scraper" -i '{"companies":["openai","notion","linear"],"publishedAfter":"25h","maxJobs":200}' \
93 --json \
94 --user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
95 2>/dev/null
96```
97
98Confirm the live schema and prices before a large batch:
99
100```bash
101apify actors info "johnvc/ashby-job-board-scraper" --json \
102 --user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
103 2>/dev/null
104```
105
106Read the rows back from a finished run:
107
108```bash
109apify datasets get-items <DATASET_ID> --format json \
110 --user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
111 2>/dev/null
112```
113
114Discover up to 100 Ashby boards from the directory and verify them live:
115
116```bash
117apify actors call "johnvc/ashby-job-board-scraper" -i '{"outputMode":"companiesOnly","maxCompanies":100}' \
118 --json \
119 --user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
120 2>/dev/null
121```
122
123Check a prospect list, including explicit misses:
124
125```bash
126apify actors call "johnvc/ashby-job-board-scraper" -i '{"companies":["Black Semiconductor","Morse Micro","Ramp","Notarealcompany Xyz"],"outputMode":"companiesOnly"}' \
127 --json \
128 --user-agent apify-awesome-skills/apify-ashby-jobs-scraper \
129 2>/dev/null
130```
131
132Every call carries the three flags this repo expects: `--json` (or `--format json`), `--user-agent apify-awesome-skills/apify-ashby-jobs-scraper`, and `2>/dev/null`.
133
134## Run it from Claude or another AI agent (MCP)
135
136The Actor is MCP-ready. Add the hosted server URL:
137
138`https://mcp.apify.com/?tools=actors,docs,johnvc/ashby-job-board-scraper`
139
140Then ask, for example: "Pull the remote engineering jobs from OpenAI and Ramp with published salary ranges, and rank them by salaryMax." MCP setup docs: https://docs.apify.com/platform/integrations/mcp
141
142## Workflow: job postings
143
1441. Start with one or two boards and `maxJobs` around 25. Look at the row shape before you pay for a wide crawl.
1452. Company names work as input. "Black Semiconductor" finds the blacksemiconductor board; the Actor tries slug spellings automatically and returns a `board_not_found` error row on a miss, optionally with `didYouMean` suggestions.
1463. Filter at the source, not downstream. `titleKeywords`, `departments`, `locationKeywords`, `employmentTypes`, `remoteOnly`, and `publishedAfter` all drop jobs before they are billed. For fully remote requests, also check `workplaceType`: `remoteOnly` can return Hybrid jobs.
1474. Keep `includeDescriptionMarkdown` on for LLM pipelines; turn it off for metadata-only rows at roughly half the per-row cost.
1485. For salary work, read the flat columns and `salaryDerived.source`. Published ranges can come from native compensation data or description parsing, even when `shouldDisplayCompensation` is false. Do not infer missing pay.
1496. Check `resultType` before treating a row as a job. An `error` row carries `errorCode` and a human-readable `errorMessage`.
1507. Dedupe downstream on `url`. It is canonical and survives a company editing the title.
151
152## Workflow: companies and prospect checks
153
1541. For directory discovery, select `outputMode: "companiesOnly"`, optionally narrow names and slugs with `discoveryQuery`, and cap the sweep with `maxCompanies`. For prospect checks, supply the requested names, slugs, or board URLs in `companies`.
1552. Keep `verifyCompanies` on for current counts; distinguish `company` rows from errors. Sort verified rows by `jobCount` within the returned sample, not as a claim about every Ashby customer. A name match is not an industry classification.
1563. Deduplicate by `boardToken`, since one company can operate multiple boards. Re-run when current counts are needed rather than presenting a cached directory snapshot as live.
157
158### Continue from companies to job postings
159
160When the request includes retrieving their jobs, keep valid `company` rows and deduplicate their non-empty `boardToken` values. Pass those values as `companies` in a second call to the same Actor with explicit `outputMode: "jobs"`, the user's filters, and a separate job cap. Stop when no valid tokens remain: an empty `companies` array triggers a directory sweep and would broaden the request.
161
162## Inputs
163
164- `companies` (array): company names, board slugs, or jobs.ashbyhq.com URLs (board, embed, or single job), mixed freely. Empty sweeps the bundled directory.
165- `startUrls` (array): the same values in URL-list form; merged with `companies`.
166- `outputMode` (enum `jobs`, `urlsOnly`, `companiesOnly`, default `jobs`)
167- `titleKeywords`, `departments`, `locationKeywords` (arrays): keep-only filters, run before billing.
168- `employmentTypes` (array of `FullTime`, `PartTime`, `Intern`, `Contract`, `Temporary`)
169- `remoteOnly` (boolean, default false)
170- `publishedAfter` (string): `24h`, `7d`, `2w`, or an ISO date.
171- `includeDescriptionMarkdown` (boolean, default true), `includeDescriptionHtml`, `includeDescriptionText` (default false)
172- `includeCompanyData` (boolean, default false): job-page enrichment, one extra request per job.
173- `report` (enum `none`, `markdown`, `html`): a whole-run digest in the key-value store.
174- `maxJobs` (integer, default 100): the primary spend cap. `maxJobsPerCompany`, `maxCompanies`, `maxConcurrency` refine it.
175- `proxyConfiguration` (object): off by default; direct connections work.
176
177Company-mode inputs:
178
179- `outputMode`: set `companiesOnly` for discovery or prospect verification.
180- `companies` (array): prospect names, slugs, or board URLs; omit it for a directory sweep.
181- `discoveryQuery` (string): case-insensitive text match over directory names and slugs.
182- `verifyCompanies` (boolean, default true): live-probe candidates; dead boards are skipped and not billed as company rows.
183- `maxCompanies` (integer, default 25): the primary cap for directory sweeps.
184- `maxConcurrency` (integer, default 5): parallel probes.
185
186## Cost
187
188Billing is pay per event with no start fee, so a run that returns nothing costs almost nothing. Confirm live prices with the info command above rather than trusting a number copied here.
189
190The base `job-result` event fires once per delivered job row, salary data included. Add-on events fire only on rows that carry the extra: `job-description-markdown` (on by default), `job-description-html`, `job-description-text`, `job-company-data`, and a flat `run-report`. Company discovery rows and URL index rows have their own cheaper events.
191
192Jobs removed by your filters are never charged. As a shape, 100 jobs with Markdown descriptions is small change.
193
194Suggested confirmation thresholds: mention the estimate under about $5, warn the user over about $5, get explicit confirmation over about $20. Present cost as "around $X", never as a guarantee.
195
196## Honest limits
197
198- **No update timestamps exist.** Ashby publishes only `publishedAt`, so `publishedAfter` gives you a new-postings feed; there is no changed-jobs feed and no field pretends otherwise.
199- Salary appears only when the employer displays compensation on the posting. Nothing is inferred by a model; `salaryDerived.source` tells you whether a value came from the structured data or a deterministic text parse.
200- Public board data only. No applicant data, no recruiter contacts, nothing behind a login.
201- One board is one request, so very large boards return in a single response; a board too large to process returns a clear in-band error rather than a partial dataset.
202- The bundled directory can omit newly launched boards. Try a direct company or board-URL check when a directory search misses a known prospect.
203- Company names come from the directory; a board outside it may use its slug as the name. One company may operate multiple board slugs, each returned as its own row.
204- Public board presence shows that a company hires through Ashby; it does not establish contract value, seats, or tenure.
205
206## Troubleshooting
207
208- `board_not_found`: the slug does not exist on the public API. Check `didYouMean` if present on the error row, or paste the board URL instead of a name.
209- `job_not_found`: a single-job URL points at a posting that closed. Fetch the whole board instead.
210- `http_error`: the source answered abnormally; the row says which HTTP status. Retry once before assuming anything.
211- Zero rows and no error row: your filters removed everything. Relax `publishedAfter` or `titleKeywords` first.
212- Duplicates across runs: dedupe on `url`, never on title.
213- Empty company sweep: loosen or remove `discoveryQuery`.
214- `jobCount` and `live` are null: `verifyCompanies` was off, so the row is a directory snapshot rather than a live read.
215
216See `references/gotchas.md` for cost guardrails and error recovery, and `references/actor-index.md` for the Actor routing table.
217
218## Related Actors
219
220- Greenhouse Job Board API: https://apify.com/johnvc/greenhouse-job-board-api?fpr=9n7kx3&fp_sid=awesomeskills
221- Workday Careers API: https://apify.com/johnvc/workday-careers-api?fpr=9n7kx3&fp_sid=awesomeskills
222- Wellfound Jobs API: https://apify.com/johnvc/wellfound-jobs-api?fpr=9n7kx3&fp_sid=awesomeskills
223- LinkedIn Jobs API: https://apify.com/johnvc/linkedin-jobs-api?fpr=9n7kx3&fp_sid=awesomeskills
224- Crunchbase Company API: https://apify.com/johnvc/crunchbase-company-api?fpr=9n7kx3&fp_sid=awesomeskills
225- LinkedIn Company API: https://apify.com/johnvc/linkedin-company-api?fpr=9n7kx3&fp_sid=awesomeskills
226- PitchBook Company API: https://apify.com/johnvc/pitchbook-company-api?fpr=9n7kx3&fp_sid=awesomeskills