LinkedIn Company Search | X-Ray | No Login | Bulk
Pricing
from $1.00 / 1,000 company founds
LinkedIn Company Search | X-Ray | No Login | Bulk
Find LinkedIn company pages by name, keyword or LinkedIn URL. No login, no cookies. Multi-country, 4 search patterns, JSON/CSV export. Pay per company, empty searches are free, per-run spend cap. HubSpot, Salesforce, Clay, n8n, Make and Zapier ready. Free plan: 100 results per run.
Pricing
from $1.00 / 1,000 company founds
Rating
0.0
(0)
Developer
Open Enrich
Maintained by CommunityActor stats
0
Bookmarked
342
Total users
126
Monthly active users
3 days ago
Last modified
Categories
Share
๐ข LinkedIn Company Search: Find Company Pages by Name | No Login
Type a company name or keyword, get back LinkedIn company page URLs with name, description and logo. No LinkedIn account, no cookies, no ban risk.
No login | 4 search patterns | Multi-country | Up to 100 results per country | JSON/CSV export
Not a scraper. We use X-ray search over publicly indexed data. We never touch LinkedIn's servers. Not affiliated with LinkedIn.
๐ณ Pricing and plans
Pay per result, see the Pricing tab. Free Apify plan: up to 100 results per run, as many runs as your Apify credit covers (the $5 monthly free credit buys about 2,500 companies). Paid plans have no per-run limit. Normal Apify platform usage applies.
Success-only billing
You pay for delivered rows only. A failed lookup, an empty search or a notice row is free: failed lookups are free. Each delivered company is one company event, charged right after the row is saved. Higher Apify plans pay less per result: Bronze 5% off, Silver 10% off, Gold and above 15% off. Exact numbers are on the Pricing tab.
Add-ons (charged extra)
Add-ons are opt-in inputs, off by default, each charged as its own event and only when it returns data for that row. The primary event is the only charge on a default run.
Delta mode
Set deltaMode to true for scheduled runs. We keep a hash of each row in a named key-value store in your own account (deltaStoreName, default linkedin-company-search-delta). Only new or changed rows are pushed and charged. The OUTPUT summary reports newRows, changedRows and skippedUnchanged.
Compatible output
Set outputFormat to compatible to get common LinkedIn scraper field names instead of ours, so existing pipelines keep working. The default is default, unchanged. The mapping table is in AGENTS.md.
โ๏ธ This vs. the alternatives
| This actor | LinkedIn's own search | Cookie-based tools (PhantomBuster, Dux-Soup) | |
|---|---|---|---|
| LinkedIn account needed | No | Yes | Yes (your cookies) |
| Account ban risk | None | n/a | Real |
| Results per search | Up to 100 per country | About 100, gated | Varies |
| Multi-country in one run | Yes, automatic | Manual | Varies |
| Output | Clean JSON/CSV via API | HTML | Varies |
| Deduplication across countries | Yes | No | Rarely |
| Incremental saving | Yes | No | Varies |
| Cost per company | Pay per result, see Pricing tab | Subscription | Subscription or per-result |
We do not claim to return more data per company than the others. We return less, on purpose: the page URL, the name, the tagline and the logo. That is exactly what you need to find the right company page without risking an account.
โก Why this actor?
- No login, no cookies. Nothing of yours is exposed. Nothing to get banned.
- Four search patterns. From "exact keyword in the title" to "broadest keyword match". You choose how strict to be.
- Countries as a list. Give
us, uk, de, frand each country gets its own search of up to 100. Duplicates across countries are removed. - Runs finish with partial results. Every company is saved the moment it is found. If a run stops, you keep what it found.
- Small and predictable output. Four fields per row. Easy to map into a CRM.
๐ฏ Use cases
- Account list building. Search "fintech" in
uk, de, then feed the URLs to linkedin-employee-search to find the people. - Competitor mapping. Search an industry keyword with pattern 3, then use company-firmographics-by-domain to get each company's domain.
- Sales prospecting. Find target companies, then run executive-email-finder-by-domain on their domains.
- Founder outreach. Find early-stage companies, then ceo-founder-email-finder-by-domain.
- Investment research. Collect startups in a niche across countries, then check people with linkedin-person-search.
- Recruiting research. Find companies in a sector to approach, then linkedin-people-search for roles inside them.
๐ Pipeline guide: from keyword to verified contact
This actor is step 1. Chain four b2bdata actors and you go from a keyword to a contact:
keyword: "fintech", countries: "uk, de"|v[1] linkedin-company-search -> company page URL, name, headline, logo|v[2] company-firmographics-by-domain -> company domain|v[3] executive-email-finder-by-domain -> decision-makers at that domain|v[4] email-phone-finder -> email / phone for the chosen person
All four are on the publisher page: See all 10 actors by b2bdata. Each step reads the previous step's dataset, so a Make or n8n scenario chains them without code. Run it as a pipeline from the Apify console, or schedule each step.
๐ Quick start
Open the actor, fill the form, press Start. Or send JSON. Three examples:
1. Find one specific company
{"keyword": "OpenAI","companyPattern": "1"}
2. Discover AI startups in four countries
{"keyword": "AI startup","companyPattern": "4","companyCountries": "us, uk, de, fr","companyMaxResults": 100}
3. Fintech in London, every page
{"keyword": "fintech","companyPattern": "3","companyCountries": "uk","companyMaxResults": 50,"loadAll": true}
โ๏ธ Inputs
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
keyword | string | Yes | none (prefill OpenAI) | Company name or search term. Exact name ("OpenAI") or broader ("AI startup", "fintech"). You can also paste a LinkedIn company URL (linkedin.com/company/...): it is converted to the company name, anything else is searched as typed, and each row shows what you typed in inputQuery and how it was read in inputRoute. |
companyPattern | string | No | "4" | Search pattern: "1" strict (exact keyword in page title), "2" moderate (keyword in title), "3" broad (phrase match), "4" broadest (default, most results). |
companyCountries | string | No | empty | Comma-separated country codes, for example uk, us, de, fr. Each country is a separate search. Empty means one global search. |
companyMaxResults | integer | No | 100 | Max company pages per country, 1 to 100. |
bulkDelayMs | integer | No | 1500 | Milliseconds between country searches, 500 to 10000. Does not affect pricing. |
loadAll | boolean | No | false | Paginate up to your max. If off, only the first page (up to 10 results) is returned. |
Pattern tips: use "1" when you know the exact name, "4" when you are exploring an industry.
Advanced inputs (API users)
These fields are hidden in the Console form and meant for API and automation use.
| Field | Type | Default | What it does |
|---|---|---|---|
maxChargeUsd | number | 0 (off) | Stops the run when this run's charges reach the amount. The run ends SUCCEEDED with the rows already delivered and one free explanation row (max_charge_reached). The check runs after each charge, so a run can exceed the amount by one result. |
sourceTag | string, up to 100 characters | empty | Copied onto every result row as sourceTag and into the OUTPUT record, so a CRM or Clay table can match results to the request that produced them. Explanation rows never carry it. |
๐ค Output
Every row carries scrapedAt (ISO timestamp of the run) and inputQuery (the query that produced it).
One dataset row per company page.
{"url": "https://www.linkedin.com/company/openai","name": "OpenAI","headline": "OpenAI is an AI research and deployment company.","photoUrl": "https://media.licdn.com/dms/image/..."}
Export as JSON, CSV, Excel, XML or HTML from the Output tab, or read the dataset over the API.
Fields you might see when present
Alongside the four fields, a row can carry searchQuery (the parameters that produced it). Instead of a data row you can get a status row:
noResults:truewhen nothing matched.error:truewhen a search failed.message: status or error details.
What is NOT returned
- โ Employee count, revenue or funding
- โ Industry, location or founding year
- โ Website or company domain (use company-firmographics-by-domain)
- โ Employees or contact details (use linkedin-employee-search)
- โ Posts, jobs or private pages
Empty fields are omitted from the row instead of being padded with placeholder values.
๐ก๏ธ Reliable results
Our data promise. We work to keep every contact current, and we stand behind it. If a record is outdated, an email bounces or a person has moved on, open the Issues tab with your run link. We review every report and sort it out with you, case by case.
- Incremental saving. Every company is saved the moment it is found. A run that stops keeps everything so far.
- Automatic deduplication. The same company URL never appears twice across countries.
- Retry with backoff. Transient failures are retried automatically before a search is given up on.
- Partial results over failure. If one country's search fails, the others still complete and you get a clear status row for the failed one.
๐ค For AI agents
This section is written for an LLM agent that calls this actor as a tool, through the Apify MCP server or the API. Humans: it doubles as a one-screen contract.
When to use this actor, and when to use a sister actor
- Use
b2bdata/linkedin-company-searchwhen you have a company name or an industry keyword and need LinkedIn company page URLs. - linkedin-employee-search: you already know the company and want its employees.
- linkedin-person-search: you know a person's name and want their profile.
- linkedin-people-search: you want people by role, keyword or location.
- linkedin-leads-verified-work-emails: you want a lead list in one call, not a single lookup.
- company-firmographics-by-domain: you have a company and need its domain.
- executive-email-finder-by-domain and ceo-founder-email-finder-by-domain: you have a domain and need decision-makers or founder emails.
- email-phone-finder: you have a person and need email or phone.
Input contract
| Field | Type | Default | Notes |
|---|---|---|---|
keyword | string | required | Company name or keyword. |
companyPattern | string, one of "1","2","3","4" | "4" | Pass a string, not a number. "1" is strictest. |
companyCountries | string | "" | Comma-separated codes, for example "us, uk". Empty is one global search. |
companyMaxResults | integer 0-100 (0 = all) | 100 | Per country. |
bulkDelayMs | integer 500-10000 | 1500 | Leave it alone. |
loadAll | boolean | false | If false, only the first page (up to 10) comes back. Set true to reach companyMaxResults. |
Required: keyword only. Send only the fields you need.
Output contract
Each item: url (string, LinkedIn company page), name (string), headline (string), photoUrl (string). Optional: searchQuery (object). Status rows carry noResults (boolean), error (boolean) and message (string) instead of company data. Nothing else is ever returned. Always check error and noResults before treating a row as a company.
Cost per call
You pay per result returned, plus Apify platform usage. An empty search costs nothing. Keep companyMaxResults low while testing. Free Apify plans get up to 100 results per run; paid plans have no per-run limit.
Idempotency and rate advice
Same input, same run. It writes a fresh dataset every time and results can change as the index changes, so do not assume two runs return identical rows. Deduplicate on url. Do not loop the same keyword. For several countries use one run with a countries list, not one run per country. Do not run more than a few runs at once.
Chaining
Take url and name from each row. To find people at a company, pass the company name or its LinkedIn URL to linkedin-employee-search. To find one named person, pass the name plus the company name to linkedin-person-search. To get a domain for step 3 and 4 of the pipeline, pass the company name to company-firmographics-by-domain. Always filter rows by error and noResults first.
Error cases and what to do
| Situation | What you see | What to do |
|---|---|---|
| Nothing matched | A row with noResults: true | Retry once with companyPattern: "4" and a broader keyword. Do not retry more than twice. |
| A search failed | A row with error: true and a message | Read message. Retry once after a minute. If it repeats, report it in the Issues tab of this actor on Apify. |
| Free Apify plan, 100 results per run reached | Run SUCCEEDED with the first 100 results plus one free explanation row (free_plan_limit) | Tell the user the free plan returns 100 results per run. Run again for the rest; a paid Apify plan removes the limit. |
| Similar names returned | Rows that look like different companies | Re-run with companyPattern: "1" and match on name. Verify before acting. |
| Invalid input | Run rejected by the input schema | Fix the field named in the error (usually companyPattern as a number instead of a string). |
Minimal call
{"keyword": "OpenAI","companyPattern": "1","companyCountries": "us","companyMaxResults": 5}
๐ Integrations: send results anywhere
Every run writes to an Apify dataset. Dataset items from LinkedIn Company Search carry url, name, headline, photoUrl. Actor id for all recipes: b2bdata/linkedin-company-search (in API URLs, write it as b2bdata~linkedin-company-search). Everything below uses the public Apify API and your own Apify token. Native means an Apify integration exists; CSV and automation routes are marked as such.
1. Fetch results over the API (native)
Send the token in a header, never in the URL. Latest successful run, as JSON, CSV or Excel:
curl -H "Authorization: Bearer $APIFY_TOKEN" "https://api.apify.com/v2/acts/b2bdata~linkedin-company-search/runs/last/dataset/items?format=json&clean=true&status=SUCCEEDED"
Swap format=json for format=csv or format=xlsx (jsonl also works). clean=true drops empty items and hidden fields. Pick fields with jq:
curl -s -H "Authorization: Bearer $APIFY_TOKEN" "https://api.apify.com/v2/acts/b2bdata~linkedin-company-search/runs/last/dataset/items?format=json&clean=true&status=SUCCEEDED" | jq '.[] | {name, url}'
Replace name and url with any field names from the output list above. For a specific run, use https://api.apify.com/v2/datasets/<datasetId>/items?format=json.
One-shot call (start a run and wait for its items, limited to 300 seconds): POST https://api.apify.com/v2/acts/b2bdata~linkedin-company-search/run-sync-get-dataset-items?format=json&clean=true with the Actor input as the JSON body and the same Authorization header. For longer runs, start the run normally and fetch the dataset afterwards.
2. Webhook on run success (native)
In the Actor's Integrations tab (or via the API) add a webhook with event type ACTOR.RUN.SUCCEEDED and your own endpoint as the request URL. Apify sends a POST with the default payload, which contains the run under resource. Your endpoint reads resource.defaultDatasetId and calls the dataset items URL from recipe 1 with it. To send a smaller body, set a custom payload template: a JSON object whose values are Apify variables in double curly braces (resource, eventType, userId, createdAt, eventData), with nested values by dot, for example the run id as resource.id and the dataset id as resource.defaultDatasetId. Switch on "Interpolate variables in string fields" in Apify Console when you quote them.
3. n8n (native node)
Apify node, operation "Run an Actor and get dataset" (or "Run an Actor", then "Get dataset items" from the Datasets resource). Select b2bdata/linkedin-company-search, paste the Actor input as JSON, and connect your Apify token as a credential. Each dataset item becomes one n8n item, so map url, name, headline, photoUrl straight into the next node. The Apify node also has an "On new Apify event" trigger for run-finished events.
4. Make (native app)
Apify app: module "Run an Actor" with b2bdata/linkedin-company-search (or the trigger "Watch Actor Runs" for scheduled or manual runs), then the search module "Get Dataset Items" using the run's default dataset id. Each returned bundle is one row, so map url, name, headline, photoUrl into your destination module.
5. Zapier (native app)
Apify app: trigger "Finished Actor run" (or action "Run Actor" with b2bdata/linkedin-company-search), then the search "Fetch dataset items" with the run's default dataset id. Map url, name, headline, photoUrl into your destination step. Add a Looping or similar step if your Zap needs one action per item.
6. Google Sheets
Apify's Store has a "Google Sheets Import & Export" Actor that you add on this Actor's Integrations tab, then choose append or replace mode and paste your spreadsheet URL. This needs a one-time Google login. Alternative with no extra Actor: Make or Zapier recipes above with their own Google Sheets module.
7. Clay (HTTP API)
In Clay, create an HTTP API request with method GET, URL https://api.apify.com/v2/acts/b2bdata~linkedin-company-search/runs/last/dataset/items?format=json&clean=true&status=SUCCEEDED, and a header Authorization: Bearer <your Apify token>. Treat each returned item as a row and chain your enrichment columns after it.
8. Airtable, HubSpot, Salesforce
No native Apify connector is used here. Two routes:
- CSV: download with
format=csv(recipe 1) or from the dataset's Export button, then use the tool's own import (Airtable CSV import, HubSpot Import, Salesforce Data Import Wizard or Data Loader). Use a unique field such as the URL as the dedupe key. - Automation: use the n8n, Make or Zapier recipe above and the CRM's module there. Their setup and field limits are theirs to define.
9. Map the fields
LinkedIn Company Search returns url, name, headline, photoUrl. Typical placement in a CRM (create custom properties where your CRM has no match):
| Output field type | Typical CRM placement |
|---|---|
| Person name | Contact name (first and last) |
| Job title or role | Contact job title |
| Company name | Company or account name |
| Website or domain | Company website or domain |
| Profile or page URL | Custom text field, also your dedupe key |
| Location (city, country) | Contact or company location fields |
| Email, phone (if returned) | Contact email, phone |
| Industry, size (if returned) | Company industry, employee count |
| Run date | Custom date field ("Sourced on") |
All recipes use the public Apify API; nothing is stored by the publisher.
๐ Schedule examples
Use Apify Schedules (cron) on a saved task.
- Weekly new-company sweep:
0 6 * * 1, keyword "AI startup", countriesus, uk. Compareurlagainst last week's dataset to find new pages. - Monthly industry refresh:
0 6 1 * *, keyword "fintech",companyMaxResults100. Send results to your CRM through a webhook. - Daily name watch:
0 8 * * *, pattern"1", one competitor name. Cheap and fast.
Keep scheduled runs small. A schedule you forget is still billed.
๐ Related actors
More from the publisher: See all 10 actors by b2bdata
- linkedin-employee-search: employees of a company.
- linkedin-person-search: find a named person.
- linkedin-people-search: people by role and keyword.
- linkedin-leads-verified-work-emails: lead lists.
- email-phone-finder: email and phone for a person.
- executive-email-finder-by-domain: decision-makers by domain.
- ceo-founder-email-finder-by-domain: founder emails by domain.
- company-firmographics-by-domain: domain for a company.
โ FAQ
Data & coverage
Q: How do I find a LinkedIn company page by name?
A: Put the name in keyword and set companyPattern to "1". You get the page URL, name, description and logo.
Q: Do I need a LinkedIn account? A: No. No account, no cookies, no login.
Q: How many companies can I get? A: Up to 100 per country per search. Four countries means up to 400 rows before deduplication.
Q: Why did I only get 10 results?
A: loadAll is off by default. With it off you get the first page only. Turn it on to reach companyMaxResults.
Q: Why do I see companies with similar names?
A: The search is keyword based. Use pattern "1" for exact names and check the name field. Always verify common names by hand.
Q: Is employee count, revenue or industry included? A: No. This actor returns the page URL, name, headline and logo. Use the pipeline above for more.
Q: Will brand-new company pages appear? A: Maybe not yet. Results come from publicly indexed data, so very new pages can be missing.
Q: Am I charged for failed lookups?
A: No. Failed lookups are free. You pay one company event per delivered company; empty results and notice rows cost nothing.
Q: What are add-ons and are they on by default? A: Add-ons are opt-in inputs, off by default. Each is its own billed event, charged only when it returns data for that row.
Q: How do I only pay for new or changed rows on a schedule?
A: Turn on deltaMode. We compare each row to a hash in a store in your account and push only new or changed ones. The summary shows newRows, changedRows, skippedUnchanged.
Q: Can I keep my existing field names?
A: Yes. Set outputFormat to compatible for common LinkedIn scraper field names. Default output is unchanged.
Legality & compliance
Q: Is this legal? A: This is not legal advice, so check your own situation. The actor never signs in to any account and collects only publicly available data, the same company pages anyone can open through a search engine. What you do with the results, including privacy and marketing rules where you operate, is your responsibility. Any legal claim or takedown request should go through Apify support (https://apify.com/contact), which passes it to us.
Q: Does it break LinkedIn's terms of service? A: The actor does not open LinkedIn or sign in with any account, so it never enters LinkedIn's user agreement. How you use the results remains your decision under the rules that apply to you.
Q: Does it collect personal data? A: It returns company pages. Company names and taglines are not personal data in themselves, but a small company page can identify a person. If you hold personal data from results, you are the data controller.
Q: Is it GDPR and CCPA compliant? A: The compliance duties sit with you as controller: lawful basis, notices, opt-outs, deletion. The Master Terms below explain who does what.
Q: Do you store my results? A: No. We keep no copy of your result data. It lives in your Apify account.
Q: Can I use the output for cold email? A: This actor returns no emails. If you add emails from another tool, you must follow anti-spam and privacy rules for each country you contact.
Q: Can I be blocked or banned? A: Your LinkedIn account cannot be, because it is never used. Your Apify account can be limited if you break the Terms below.
๐ Support
Use the Issues tab on this actor's Apify page for bugs, questions and feature requests. We answer within 24 hours on working days. Please include the run ID and the input you used.
๐ Legal
Use for B2B prospecting only. Comply with all applicable laws including GDPR, CCPA, and CAN-SPAM.
Not affiliated with LinkedIn. The LinkedIn name belongs to its respective owner. This actor finds company page URLs through publicly indexed data. It does not log in, use cookies, access private pages or bypass authentication. Published on Apify by b2bdata as proprietary software.
๐ Master Terms of Service
Publisher: b2bdata (the "Publisher"), an independent developer publishing on the Apify platform. Applies to: LinkedIn Company Search (the "Actor"). Version: 1.0.
Acceptance by use
By running the Actor, calling it through the Apify API, the Apify MCP server or any integration, or letting a schedule or an AI agent run it for you, you accept these Terms. This is acceptance by use. No signature is needed.
If you run the Actor on behalf of a company, you confirm you may bind that company. If you do not accept these Terms, do not run the Actor. Continued use after we update the Terms is acceptance of the update. Anonymous or automated use does not remove your responsibility: the Apify account that starts the run is the accountable party.
Preamble: how the Actor is built
The Actor is a thin wrapper over an independent search index. It does not log in to anything, does not use cookies or accounts, and does not fetch pages from the source platform. We are a software vendor. We ship code that turns a query into a structured result. We do not own, host or curate the underlying data.
You / your agent| input (query, filters)vThe Actor (the Publisher's code, runs on Apify)| search requestvAn independent search index of publicly indexed data| public result rowsvThe Actor (normalises, deduplicates, saves to your dataset)|vYour Apify dataset (you control it)
Each party has one job. The index holds publicly indexed data. The Actor reshapes it. You decide what to search for, what to keep and what to do with it. We keep no copy of your queries or your results once the run ends, beyond what Apify itself stores in your account and what we need for billing and abuse prevention.
1. Nature of the service
1.1 What the Actor is
A software tool that searches publicly indexed data and returns structured rows to your Apify dataset. It is a data-discovery utility, nothing more.
1.2 What the Actor is not
It is not a scraper of the source platform, not an official integration, not a credit bureau, not a background-check service, not an employment or tenant screening tool, and not a source of legal, financial or compliance advice. Results are leads and pointers. They are not verified facts.
1.3 The publisher's limited role
We write and maintain the code. We do not review individual runs, individual results or individual users. We do not guarantee that a result is accurate, current, complete or lawful to use for your purpose.
1.4 Third-party infrastructure
The Actor depends on the Apify platform and on an independent search index. We do not control either. Their availability, rules and changes can affect the Actor at any time.
2. Who may use the Actor
2.1 Eligibility
You must be at least 18, have the legal capacity to contract, and not be barred from using the Apify platform or from receiving services under applicable sanctions or export laws.
2.2 Your representations
By running the Actor you represent that you have a lawful purpose, that you will follow the laws that apply to you and to the people whose data you handle, and that the information on your Apify account is accurate.
3. Permitted uses
Lawful business uses, including market research, account and lead discovery, competitive analysis, recruiting research done in line with local law, investment research, data enrichment of records you are entitled to hold, and building your own internal tools. Any use must comply with Section 4 and Section 6.
4. Prohibited uses
4.1 Illegal activity
Any use that violates a law or regulation that applies to you, to us or to the people in the data.
4.2 Harassment, stalking and personal targeting
Locating, monitoring, intimidating or pressuring a private individual.
4.3 Discrimination
Using results to exclude or disadvantage people on a protected characteristic, including in hiring, lending, housing or insurance decisions.
4.4 Spam and unsolicited commercial communication
Sending bulk messages in breach of anti-spam, e-privacy or telemarketing rules (for example CAN-SPAM, PECR, CASL, GDPR consent rules).
4.5 Fraud and deception
Phishing, impersonation, social engineering, fake profiles or any scheme to mislead.
4.6 Source platform abuse
Using the Actor to evade a block, rate limit or enforcement action by the source platform, or to build a service that competes with the source platform by copying its data wholesale.
4.7 Reselling the Actor's service
Reselling or sub-licensing access to the Actor, or republishing raw output as a competing data product, without our written permission.
4.8 AI training without authorization
Using raw output to train a model that identifies or profiles individuals, without a lawful basis and without checking the source platform's terms.
4.9 Sensitive targeting
Building lists based on health, religion, ethnicity, political opinion, sexual orientation, union membership, immigration status, criminal history or any other special category of data.
4.10 Privacy law violations
Any processing of personal data without a lawful basis, without required notices, or in breach of a data subject's rights.
5. Source platform terms: your responsibility
5.1 Acknowledgment
The source platform named in the Addendum has its own terms. We have no contract with you about them and we do not interpret them for you.
5.2 Your sole responsibility
You alone are responsible for checking whether your use of results is allowed under the source platform's terms and under the law of your jurisdiction. Running the Actor is not a statement by us that your use is allowed.
5.3 Cease-and-desist compliance
If the source platform, a rights holder or a regulator sends us a valid cease-and-desist or takedown notice about specific use of the Actor, we will act on it. If we forward such a notice to you, you must stop the named use within 48 hours of receipt and confirm in writing. We may suspend your access immediately while we assess the notice.
6. Data protection
6.1 Roles under privacy law
For the data you collect with the Actor, you are the data controller (or business, under CCPA). Apify and its infrastructure act for you as processor or service provider under their own terms. We, as the publisher of the code, do not decide the purposes or means of your processing and do not receive your result data.
6.2 No data retention by the publisher
We do not retain your result data. We do not build a database from your runs. We keep only what is needed for billing, security and abuse prevention, such as run metadata and support correspondence.
6.3 Your obligations as data controller
You must have a lawful basis (GDPR, UK GDPR), give required notices, honour access, deletion and objection requests, respect opt-outs and "do not sell or share" rights (CCPA/CPRA), keep records, protect the data, and delete it when you no longer need it.
6.4 Sensitive data targeting
You must not use the Actor to target special-category data (see 4.9). If sensitive data appears in results, you must delete it or handle it under the stricter rules that apply.
6.5 Data subject requests
If a person contacts us about data you collected, we will refer them to you and may ask you to confirm you have handled the request.
7. Intellectual property
7.1 Actor code
The Actor, its code, schemas, documentation and branding belong to the Publisher. This is proprietary software. No licence is granted except the right to run the Actor under these Terms.
7.2 Output data
We claim no ownership of the output. Rights in underlying data belong to their owners. You are responsible for how you use it.
7.3 Restrictions
No reverse engineering, copying of the Actor, or removal of notices, except where the law gives you that right regardless.
7.4 Feedback
If you send feedback or bug reports, we may use them freely to improve the Actor, without payment, and without crediting you.
8. Pricing and payment
8.1 Apify platform billing
Charges are set on the Actor's Pricing tab and billed by Apify. Platform usage costs may also apply, as shown by Apify. We do not handle your payment details.
8.2 Pricing changes
We may change prices. For any increase we give at least 14 days' notice through the Apify platform's change-notification process before it takes effect.
8.3 No refunds for misuse
Results delivered as described are billable. Charges for runs you configured wrongly, repeated by a schedule you forgot, or started by an agent you control are your responsibility. Refund requests for platform or Actor faults go through Apify support or to us.
9. Service availability and changes
9.1 No uptime guarantee
We give no uptime, latency, volume or coverage guarantee. Runs can return fewer results than you asked for, or none, because the underlying index changes.
9.2 Service discontinuation
We may change, limit or stop the Actor at any time. We will try to give notice on the Actor page when practical.
10. Disclaimers
10.1 "As is" service
The Actor is provided "as is" and "as available", without warranties of any kind, including merchantability, fitness for a particular purpose, accuracy and non-infringement.
10.2 No representation of lawfulness
We do not represent that your intended use is lawful.
10.3 No endorsement of source content
Results are not endorsed, verified or vouched for by us. Names can be wrong, profiles can be outdated and similarly named entities can be mixed up.
11. Limitation of liability
11.1 Aggregate cap
To the maximum extent the law allows, our total liability for all claims relating to the Actor is limited to the greater of USD 100 or the fees you paid for the Actor in the 3 months before the event that gave rise to the claim.
11.2 Excluded damages
We are not liable for indirect, incidental, special, consequential or punitive damages, or for lost profit, lost revenue, lost data or lost goodwill, even if advised of the possibility.
11.3 Time limit
Any claim must be brought within 1 year after it arose.
12. Indemnification
12.1 Your indemnification of the publisher
You will indemnify and hold harmless the Publisher, its owners and contractors from claims, losses and reasonable legal costs arising from your use of the Actor or its output, your breach of these Terms, or your violation of any law or third-party right.
12.2 Defense
We will tell you promptly about a claim. You may control the defense, but you may not settle in a way that admits fault for us without our written consent.
12.3 Scope
This applies whatever the legal theory, and survives termination.
13. Suspension and termination
13.1 Termination by the publisher
We may suspend or end your access at any time, with or without notice, especially for a breach of Section 4 or a valid notice under 5.3.
13.2 Effects of termination
Rights to run the Actor stop. Sections that by nature survive (IP, disclaimers, liability, indemnification, disputes) continue.
13.3 Termination by you
Stop running the Actor and delete your schedules and integrations.
14. Dispute resolution
14.1 Informal resolution first
Before any formal action, raise the dispute through Apify support or the Actor's issue tab on Apify, and allow 60 days for a good-faith resolution. The Issues tab is for product questions only and is not a channel for legal notices.
14.2 Apify's process next
If the informal step fails, raise the matter through Apify's dispute and support channels. Your contractual relationship for payment, refunds and platform access is with Apify, under Apify's Terms of Service.
14.3 No chosen court
These Terms do not select a governing law or a court. Any claim that survives 14.1 and 14.2 is subject to the law and forum that apply by default to a dispute between you and an individual software developer reached through Apify.
14.4 No class actions
Claims may be brought only on an individual basis, not as a plaintiff or class member in a class, collective or representative action.
14.5 Attorneys' fees
The prevailing party may recover reasonable attorneys' fees where the law allows.
15. Miscellaneous
15.1 Entire agreement
These Terms, with the Addendum, are the whole agreement about the Actor. Apify's own terms continue to apply to the platform.
15.2 Severability
If a provision is unenforceable, the rest stays in force.
15.3 Assignment
You may not assign these Terms. We may assign them in a merger, sale or reorganisation.
15.4 Force majeure
Neither party is liable for delay caused by events beyond reasonable control, including outages of the platform or of upstream infrastructure.
15.5 Third-party beneficiaries
There are none, except that the Publisher's owners, contractors and affiliates may enforce the protections in Sections 10 to 12.
15.6 Survival
Sections 5, 6, 7, 10, 11, 12 and 14 survive termination.
15.7 Language
The English text controls.
15.8 Publisher identification for legal process
All legal notices, takedown requests, cease-and-desist letters, regulator enquiries and data-subject requests must be directed to Apify (https://apify.com/contact), which forwards them to the Publisher. The Publisher operates on Apify under the username b2bdata. The Publisher's identity is held by Apify for billing and is provided to courts and authorities through valid legal process directed via Apify's official channels. We do not publish personal details on the Actor page.
16. Acknowledgment
By running the Actor you confirm you have read these Terms, that you understand you act as the data controller of what you collect, and that you are responsible for lawful use.
๐ก๏ธ Actor-Specific ToS Addendum: LinkedIn Company Search
A. Architectural disclosure
The actor sends your keyword to an independent search index of publicly indexed data and returns the matching company page URL, name, headline and logo URL. It does not call LinkedIn, does not log in and does not use cookies.
B. Source platform
The source platform is LinkedIn. LinkedIn is not affiliated with, and has not endorsed, this actor. Your use of LinkedIn data is governed by LinkedIn's terms and by the law that applies to you (Section 5 of the Master Terms).
C. Output and accuracy
Results may include similarly named companies, out-of-date taglines or missing pages. Treat output as leads to verify, not as verified facts.
D. No personal contact data
This actor returns no emails and no phone numbers. If you combine its output with data from other actors or tools, you take on the duties for that combined data.
E. Limits
Up to 100 results per country per search. Free Apify plans get up to 100 results per run; paid plans have no per-run limit.
F. Feedback
Problems or ideas? Use b2bdata/supporter-feedback (free, no rewards) or post in this actor's Issues tab.
G. Takedown
If a company page owner or LinkedIn asks that specific use of this actor stop, send the request through Apify (https://apify.com/contact) or the actor's issue tab, not to the support email. Section 5.3 of the Master Terms (48 hours) applies.