/blind/companies/reviews

POST /api/blind/companies/reviews

Price: 20 credits

Get Blind (teamblind.com) employee reviews for a company by name or profile URL

How to use it

Get Blind (teamblind.com) anonymous employee reviews for a company by name/alias (URL segment like 'Google') or profile URL. Each review has an overall rating and category ratings (career growth, work life balance, compensation, culture, management), pros, cons, reason for resignation, the reviewer's anonymous handle, job title, location, tenure years and helpful count. Only the recent public review slice is returned; the full review corpus is gated behind Blind's contribute-to-unlock wall.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Company name/alias (the URL segment, e.g. 'Google') or a full company profile URL (examples: "Google", "Microsoft", "https://www.teamblind.com/company/Google"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)

Response

• @type string (default: "BlindReview")
• id integer required
• alias string nullable
• document_title string nullable
• pros string nullable
• cons string nullable
• reason_resign string nullable
• rating number nullable
• career_rating number nullable
• work_life_balance_rating number nullable
• compensation_rating number nullable
• culture_rating number nullable
• management_rating number nullable
• author_nickname string nullable
• job_title string nullable
• location string nullable
• location_country_code string nullable
• employee_status string nullable
• member_start_year integer nullable
• member_end_year integer nullable
• helpful_count integer nullable
• created_at integer nullable
• company string nullable

Errors

• 422 — 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 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.