POST /api/glassdoor/companies
Price: 10 credits
Get a Glassdoor (glassdoor.com) company overview by employer id (or company URL): name, rating, ratings by category, recommend/CEO-approval/business-outlook percentages, review/salary/job counts, industry, sector, headquarters, size, revenue, founding year, company type, website, description, mission, CEO, workplace awards and competitors.
Fetch a single Glassdoor company by employer id (numeric, IE-prefixed, E-prefixed, or a company URL). Returns one item with id, name, short_name, url, image, website, headquarters, size, size_category, company_type, revenue, founded_year, description, mission, industry, sector, review_count, salary_count, job_count, photo_count, benefit_count, rating (overall 1-5), ratings (career_opportunities, compensation_and_benefits, culture_and_values, diversity_and_inclusion, senior_management, work_life_balance on a 1-5 scale, plus recommend_to_friend, ceo_approval and business_outlook as 0-1 fractions), ceo (name, title, image), awards (name, year) and competitors (id, name, short_name).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)company string required — Glassdoor employer id (e.g. 7633, IE7633 or E7633) or a company URL containing it (examples: "7633", "IE7633", "https://www.glassdoor.com/Overview/Working-at-NVIDIA-EI_IE7633.11,17.htm"; minLength: 1)country string — Country edition (default: "us"; one of: "us", "gb", "ca", "de")@type string (default: "GlassdoorCompany")id string requiredname string nullableshort_name string nullableurl string nullableimage string nullablewebsite string nullableheadquarters string nullablesize string nullablesize_category string nullablecompany_type string nullablerevenue string nullablefounded_year integer nullabledescription string nullablemission string nullableindustry string nullablesector string nullablereview_count integer nullablesalary_count integer nullablejob_count integer nullablephoto_count integer nullablebenefit_count integer nullablerating number nullableratings object nullable@type string (default: "GlassdoorCompanyRatings")overall number nullablecareer_opportunities number nullablecompensation_and_benefits number nullableculture_and_values number nullablediversity_and_inclusion number nullablesenior_management number nullablework_life_balance number nullablerecommend_to_friend number nullableceo_approval number nullablebusiness_outlook number nullableceo object nullable@type string (default: "GlassdoorCompanyCeo")name string nullableimage string nullableawards array (default: [])@type string (default: "GlassdoorCompanyAward")name string requiredyear integer nullablecompetitors array (default: [])@type string (default: "GlassdoorCompetitor")id string requiredname string nullableshort_name string nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — Company not found (well-formed but nonexistent employer id) Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.