Glassdoor API — Authentication — FetchLayer Docs
Documentation menu
FetchLayer FetchLayer API

Authentication

All requests use your FetchLayer API key as a Bearer token. No Glassdoor account, employer login, or partner credential is required, and nothing about the caller is sent to Glassdoor.

Sending requests

Every endpoint is a POST with a JSON body. There is no GET surface and no media passthrough on this platform.

bash
curl -X POST https://api.fetchlayer.dev/glassdoor/company-reviews \
  -H "Authorization: Bearer ss-your-key" \
  -H "Content-Type: application/json" \
  -d '{"company":"671954","limit":30}'

Keep your key secret

Only use API keys in server-side code and rotate a key immediately if it is exposed.

What a request costs

One request is one credit, and each page walked is one request — so pages: 10 on the reviews or interview-reports endpoint bills as ten. /resolve-url is the exception: parsing a URL consumes nothing, so resolving before fetching is never penalised.

Authentication errors

A missing or invalid key returns HTTP 401.

json
{
  "error": "Invalid API key"
}