LinkedIn company data in Clay
A column of URLs becomes employee counts, industries, and numeric ids.
What data do you get?
Point one HTTP column at each public company URL. It fills in the fields people filter on, and joins back on the numeric LinkedIn id. Nothing to install, and it runs on any Clay plan that allows HTTP enrichments.
A real company response, not a mockup
This is the exact JSON a company call returns for linkedin.com/company/stripe, trimmed for width. Current charges use the LinkedIn read rate shown below.
accessible is false for a private or dead page, and that row is free. company.linkedInId is LinkedIn's permanent numeric company id, so it is the stable key to join this data back to your other tables.
One HTTP API column in Clay
CrustAPI is a plain HTTP endpoint, so you use Clay's built-in HTTP API enrichment. About two minutes, no code.
- Add the enrichment In your table, click Add enrichment, search HTTP API, and open the Configure tab.
- Set the method and endpoint Choose GET, then paste the URL below into API endpoint URL. Type / where the company URL goes and pick your column.
- Add your key as a header Under Header fields, add X-API-Key with your key. Save it once as a header account so it is not left in plain text.
- Pick fields, then Test List what you want under Field paths to return, like company.employeeCount, then hit Test on one row before running the table.
Want to see the shape first? The same call as a one-line curl:
Map our fields to Clay columns
Real field paths from the sample above. Point each Clay column at the path on the left.
| Clay column | Response field | Value in the sample |
|---|---|---|
| Company name | company.name | Stripe |
| Employees (exact) | company.employeeCount | 17103 |
| Industry | company.industry | Technology, Information and Internet |
| Headquarters | company.headquarters | South San Francisco, California |
| Founded | company.founded | 2010 |
| Followers | company.followers | 1625548 |
| Website | company.website | https://stripe.com |
| LinkedIn numeric id | company.linkedInId | 2135371 |
| Accessible flag | accessible | true |
The company call returns company.linkedInId by default, no flag needed (the highlighted row). On the profile call, the company and school ids attached to a person are opt-in with companyId=true and schoolId=true.
How much does each row cost?
Pay per successful company row. Rows that come back accessible: false are free, so a messy list never inflates the bill.
| Deposit | Google Search / 1,000 requests | Maps / 1,000 businesses | LinkedIn Profiles / 1,000 | LinkedIn Companies / 1,000 | LinkedIn Posts / 1,000 requests | People, Jobs, Refresh / 1,000 units |
|---|---|---|---|---|---|---|
| $10+ | $1.00 | $1.96 | $4.00 | $3.00 | $6.00 | $1.96 |
| $149+ | $0.76 | $1.49 | $3.00 | $2.50 | $4.50 | $1.49 |
| $549+ | $0.56 | $1.10 | $2.50 | $2.00 | $3.30 | $1.10 |
| $1,999+ | $0.41 | $0.80 | $2.00 | $1.75 | $2.45 | $0.80 |
| $6,500+ | $0.33 | $0.65 | $1.75 | $1.60 | $1.95 | $0.65 |
| $27,500+ | $0.28 | $0.55 | $1.60 | $1.50 | $1.65 | $0.55 |
| $50,000+ | $0.26 | $0.50 | $1.50 | $1.50 | $1.50 | $0.50 |
| $100,000+ | $0.20 | $0.40 | $1.50 | $1.50 | $1.50 | $0.40 |
Every eligible account gets $6 of free usage monthly. Each deposit keeps its prices until spent; paid funds never expire. People and Jobs bill per successful search, Refresh per accessible profile. Full profiles in People use the read rate per full profile. See all billing details.
Larger deposits unlock lower endpoint prices. Each deposit keeps its prices until spent. See the full deposit table on the pricing page. Prices in USD, ex-tax.
Funds are prepaid and never expire, so a pack you buy for one Clay project is still there for the next one.
Who uses this recipe?
- Clay power users. One more HTTP column in the waterfall, with live firmographics and a stable join key.
- GTM engineers. Score and route accounts on exact employee counts instead of stale size bands.
- Agencies. Enrich a client's account list in minutes and hand back a table with industry, HQ, and size filled in.
- RevOps. Join the enriched rows back to the CRM on company.linkedInId, not a name string.
Related: LinkedIn Company API · LinkedIn API · All integrations · Company profiles and example data
Common questions
Click Add enrichment, search HTTP API, and open the Configure tab. Choose GET, paste https://crustapi.com/v1/linkedin?type=company&url= and type / to pick your company URL column, then add an X-API-Key header with your key. List the fields you want under Field paths to return, like company.employeeCount and company.linkedInId, then hit Test.
It is an HTTP call, and we say so plainly. CrustAPI is one endpoint, so you wire it in with Clay's HTTP API enrichment column rather than a native CrustAPI app. Anything in Clay that can make an HTTP GET can call it, and there is nothing to install.
name, universalName, tagline, description, website, industry, companySize, employeeCount, employeeCountRange, headquarters, locations, companyType, founded, followers, and the numeric linkedInId, all as clean JSON. List the paths you want under Field paths to return. company.linkedInId is a permanent numeric id, so it is the right stable key for joins.
Company lookups bill per successful request. Clay runs the column once per row, so standard pricing is $0.006 per row that returns a company. Inaccessible or missing pages are free. Paid funds never expire.
We read only the public, logged-out company page, the same page anyone can open without signing in. There are no fake accounts and no logins involved on our side. A site's terms govern its own logged-in access; what comes back here is data that is public to any visitor.
Enrich your first Clay table today
Start free, no card needed. Add one HTTP API column, point it at the company endpoint, and watch employee counts, industries, and numeric ids fill in down the table. Companies that are not accessible cost you nothing.
Try for free