Browse All Salary Reports at a Company
View all Glassdoor Employer Data endpoints →The full salary surface for one employer as a sorted, paginated list — the complement to the single-estimate company-salaries endpoint. Pass company_id and optionally narrow by job_title or location (with location_type); sort by MOST_SALARIES (roles with the most reports), HIGH_TO_LOW (highest pay first) or MOST_RECENT (freshest reports first), and page through the list with page. Rows follow the per-role salary layout of the employer's public salaries page, so the feed drops straight into distribution charts, spreadsheets and trend trackers without querying one title at a time.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/glassdoor/company-salaries-v2 API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/glassdoor/company-salaries-v2?key=<API_KEY>&company_id=9079&page=1'
Query Result
Use Cases
- Salary distribution charts across every reported role at one company
- CSV export of salary rows for compensation-committee or consulting analysis
- Quarterly trend tracking of pay reports at a target employer sorted by recency
- Org-wide pay mapping ahead of interview prep or acquisition diligence
Frequently asked questions
How do I bulk-collect a company's salary data?
Page through the endpoint to walk every job title with reported salaries at that company; sort by MOST_SALARIES to harvest the richest samples first, then persist rows for distribution and percentile analysis.
How is this different from the single-point salary estimate endpoint?
The single-point endpoint returns one confidence-tagged summary per company and title; this endpoint returns the whole company as a per-title salary list — better for distributions, rankings and trends.
Can I narrow to one city or job family?
Pass a job_title keyword plus location and location_type; filters apply server-side and stay consistent across pages.