Glassdoor reviews data API

What you can request

Every request reads the inputs below.

Every request also takes maxItems (records for the whole request) and maxItemsPerInput (records per search, URL or name).

Example request and record

The request below is the one this example record answers. The names, usernames, photos and contact details of people in it are fictional. Long values in the record are shortened.

curl -X POST https://api.urakimon.com/records/glassdoor \
  -H "x-api-key: $URAKIMON_API_KEY" \
  -H "content-type: application/json" \
  -d '{
    "employerIds": ["9079"],
    "reviewSort": "recent",
    "maxItemsPerInput": 150
  }'

import os
import requests

res = requests.post(
    "https://api.urakimon.com/records/glassdoor",
    headers={"x-api-key": os.environ["URAKIMON_API_KEY"]},
    json={
        "employerIds": [
            "9079"
        ],
        "reviewSort": "recent",
        "maxItemsPerInput": 150
    },
)
res.raise_for_status()
records = res.json()["records"]

const res = await fetch("https://api.urakimon.com/records/glassdoor", {
  method: "POST",
  headers: {
    "x-api-key": process.env.URAKIMON_API_KEY,
    "content-type": "application/json",
  },
  body: JSON.stringify({
    "employerIds": ["9079"],
    "reviewSort": "recent",
    "maxItemsPerInput": 150
  }),
});
const { records } = await res.json();

{  "source": "glassdoor",  "type": "review",  "id": "105649533",  "url": "https://www.glassdoor.com/Reviews/Employee-Review-Google-RVW105649533.htm",  "employerId": 9079,  "employerName": "Google",  "title": "Strong investment in seller development, but slow processes",  "rating": 5,  "subRatings": {    "workLife": 5,    "culture": 5,    "career": 5,    "compensation": 4,    "management": 4,    "diversity": 5,    "recommend": "POSITIVE",    "ceo": "APPROVE",    "outlook": "POSITIVE"  },  "pros": "Lots of investment in development of sellers",  "cons": "Takes time to get things done",  "advice": null,  "employerResponse": null,  "employerResponses": [],  "employerResponseCount": 0,  "reviewedAt": "2026-09-18T21:39:40.660Z",  "jobTitle": "Account Executive",  "location": {    "text": "New York, NY",    "type": "CITY",    "id": 1132348  },  "employmentStatus": "REGULAR",  "isCurrentEmployee": true,  "lengthOfEmployment": 4,  "isFeatured": false,  "helpfulCount": 0,  "notHelpfulCount": 0,  "language": "eng",  "event": "review",  "collectedAt": "2026-09-20T19:43:59.965Z"}

Fields

Every record starts with the same envelope: source, type, event, id, url, collectedAt. What the envelope means. The tables below list the fields after it, read from real Glassdoor records. Where a field does not apply to an item it is null or an empty list, not left out. "Present on" names the billed events a field comes with when it is not on every record of that type.

review records

One employee review of a single employer. Billed as review.

employer records

One employer's profile page, with its aggregate review ratings. Billed as employer-detail.

Glassdoor data pricing

You pay once for each record you receive, at the price of the event it carries. A request that returns nothing costs nothing.

All pricesHow billing works

Freshness and limits

• Records are collected when you send the request. Each one carries collectedAt, the UTC time it was read.
• POST /records/glassdoor returns up to 500 records in one response. Ask for more and it answers 413; send the same body to POST /jobs/glassdoor instead.
• A request without maxItems returns up to 100 records.
• Your key's rate limit and quotas apply to every source.

Next steps

• Make your first request
• Choose between records and jobs
• Rate limits and quotas
• Get a signed webhook when a job finishes