/blind/layoffs/search

POST /api/blind/layoffs/search

Price: 20 credits

Search the Blind (teamblind.com) layoff tracker (WARN filings + community-reported layoffs)

How to use it

Search the Blind (teamblind.com) layoff tracker, which aggregates WARN filings and community-reported tech-and-beyond layoffs. Filter by company name, tracked status (rumor/confirmed/in progress/completed), size bucket, industry, location and date range, and sort by recency, size or company. Each record has the company, layoff date, number and percent laid off, HQ and layoff location, industry tags, status, and any linked news article. Covers the most recently tracked layoffs.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string — Filter by company name substring (default: ""; examples: "Google")
• status string nullable — Filter by tracked status (one of: "rumor", "confirmed", "in_progress", "completed")
• severity string nullable — Filter by layoff size bucket (one of: "small", "medium", "large")
• industry string — Filter by industry substring (default: ""; examples: "FinTech")
• location string — Filter by layoff or HQ location substring (default: ""; examples: "India")
• date_from string — Only layoffs on/after this date (YYYY-MM-DD) (default: ""; examples: "2026-06-01")
• date_to string — Only layoffs on/before this date (YYYY-MM-DD) (default: ""; examples: "2026-07-31")
• sort string — Result ordering (default: "recent"; one of: "recent", "oldest", "most_laid_off", "company")
• count integer required — Max number of layoff records to return (min: 1)

Response

• @type string (default: "BlindLayoff")
• id string required
• company_name string required
• company_alias string nullable
• company_image string nullable
• industries array (default: [])
• headquarters string nullable
• layoff_location string nullable
• layoff_date string nullable
• date_precision string nullable
• laid_off_count integer nullable
• laid_off_percent number nullable
• total_employees_before integer nullable
• status string nullable
• severity string nullable
• is_verified boolean nullable
• source_url string nullable
• discussion_url string nullable
• news_url string nullable
• news_title string nullable
• news_source string nullable
• news_summary string nullable
• notes string nullable
• created_at integer nullable
• updated_at integer 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 — The entity was not found, or a precondition failed 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.