/yc/search/companies

POST /api/yc/search/companies

Price: 1 credit

Search YC companies with filters

How to use it

Search Y Combinator companies by keyword, industry, region, batch, team size, and hiring status. Industry values are YC-specific categories, not free text. Common values: AI, Developer Tools, Healthcare, Fintech, Education, Enterprise, Consumer, Biotech, Climate, Security. Batches accept full names ('Winter 2024', 'Summer 2013', 'Fall 2024', 'Spring 2025') or short codes ('W24', 'S13', 'F24', 'X25' — X means Spring).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string — Text search query (default: "")
• industries array nullable — Filter by industries (e.g., 'Healthcare', 'B2B')
• regions array nullable — Filter by regions (e.g., 'Latin America', 'Europe')
• batches array nullable — Filter by YC batches — full names ('Winter 2024') or short codes ('W24', 'X25')
• is_hiring boolean nullable — Filter by hiring status
• nonprofit boolean nullable — Filter by nonprofit status
• top_company boolean nullable — Filter by top company status
• team_size_min integer nullable — Minimum team size (min: 1)
• team_size_max integer nullable — Maximum team size (max: 10000)
• count integer required — Max result count (>: 0)
• sort_by string — Sort results by relevance or launch date (default: "relevance"; one of: "relevance", "launch_date")

Response

• @type string (default: "YCCompany")
• id integer required
• name string required
• slug string required
• website string nullable
• one_liner string nullable
• long_description string nullable
• team_size integer nullable
• industry string nullable
• subindustry string nullable
• industries array (default: [])
• regions array (default: [])
• batch string nullable
• status string nullable
• stage string nullable
• tags array (default: [])
• is_hiring boolean nullable
• nonprofit boolean nullable
• top_company boolean nullable
• launched_at integer nullable
• all_locations string nullable
• small_logo_thumb_url string nullable
• former_names array (default: [])
• app_video_public boolean nullable
• demo_day_video_public boolean nullable
• app_answers boolean nullable
• question_answers boolean nullable
• founders array (default: [])
  • @type string (default: "YCFounder")
  • name string required
  • bio string nullable
  • linkedin_url string nullable
  • twitter_url string nullable
  • avatar_url string nullable
• jobs array (default: [])
  • @type string (default: "YCJob")
  • location string nullable
  • salary_range string nullable
  • url string nullable
• social_links object nullable
  • @type string (default: "YCSocialLinks")
  • linkedin string nullable
  • twitter string nullable
  • facebook string nullable
  • crunchbase string nullable
  • github string nullable
• year_founded integer nullable
• city string nullable
• country string nullable
• logo_url string nullable
• news_items array (default: [])
  • @type string (default: "YCNewsItem")
  • url string required
  • date string nullable
• launches array (default: [])
  • @type string (default: "YCLaunch")
  • url string nullable
  • date string nullable
• company_photos array (default: [])
  • @type string (default: "YCPhoto")
  • url string required
  • photo_type string nullable
• primary_partner object nullable
  • @type string (default: "YCPartner")
  • name string required
  • url 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 — 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.