Search Companies by Name

View all Glassdoor Employer Data endpoints →

Resolve any employer name or keyword to its Glassdoor company record. Pass query (e.g. google) and receive data, a ranked array of matching employers. Each hit carries the company_id token used by every other endpoint in this project, plus name, rating, review_count, salary_count, job_count, headquarters_location, logo, company_size, industry, website and company_link. Set limit (1-100, default 10) to control how many hits come back. This is the front door of the dataset: run it once to resolve a name, then feed company_id into the overview, reviews, salaries, jobs and interviews endpoints. Verified live: a search for google returns Google (company_id 9079) first with a 4.4 rating and Mountain View headquarters.

API Features

Name-to-ID resolution Every hit returns the company_id token that the overview, reviews, salaries, jobs and interviews endpoints accept.
Ranked employer matches Results come back relevance-ranked with rating, review and salary counts to disambiguate similar names.
Up to 100 hits per call Set limit to widen autocomplete-style searches or keep it small for fast pickers.
Rich identity fields Logo URL, headquarters location, industry and company size ride along, so pickers render without a second call.

Live API Demo

GET /api/project/glassdoor/company-search

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/glassdoor/company-search?key=<API_KEY>&query=google&limit=10'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Does Glassdoor have an official API?

Glassdoor no longer offers a public developer API. This project packages company search, reviews, salaries and job listings into stable JSON endpoints — one authenticated call returns results, with no scrapers, proxy pools or login sessions to maintain yourself.

How do I get a Glassdoor company ID?

Pass the employer name to query and take company_id from the top hit (for example, Google is 9079). Every company-scoped endpoint in this project accepts that ID; for batch workloads, cache the name-to-ID mapping.

How do I pick the right company when several share a name?

Hits are relevance-ranked and carry rating, review count, headquarters and industry fields — use them to disambiguate in your UI, or pin the first hit and log the alternatives.

Related operations

Guides

View Subscription Plans →