Glassdoor API v1
Four employer-data surfaces behind one company id — ratings, employee reviews, reported pay and candidate interview reports — from https://api.fetchlayer.dev/glassdoor. No Glassdoor account, no partner agreement, no HTML parsing.
Available endpoints
What the data does and does not cover
Three limits are real and upstream. They are stated here rather than discovered later, because a response that hits one of them still comes back well formed.
- Salaries are the first page only.
/company-salariestakes nopagesand nocursor: the upstream salaries listing is not routed past page one.limittrims what comes back from that page; it does not walk further. Read the result as the most-reported roles at a company, not every role. - Sorting is local.
sortByon/company-reviewsorders the reviews collected in that response, over the window yourpagesandlimitdefined. It is not a sort across the company's whole review history, so sorting by date on one page of a 40,000-review company returns the newest of that page. - Every response carries
notes. It is an array of plain-language strings reporting a walk that stopped short, a listing with more pages, or an upstream limit that was hit. Read it on every call: it is where an incomplete answer says so.