/crunchbase/search

POST /api/crunchbase/search

Price: 20 credits

Search Crunchbase companies by filters

How to use it

Search Crunchbase companies by keywords, location, industry, employee count, and other filters. The valuation, valuation date and IT spend filters are not supported and return 422.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keywords union — Description keywords. Example: 'FinTech' or ['RegTech', 'FinTech'] (default: []; examples: "FinTech")
• location union — HQ locations. Example: 'Boston' or ['San Francisco', 'Boston'] (default: []; examples: "San Francisco")
• postal_code union — HQ postal codes. Example: '94105' or ['94105', '10001'] (default: []; examples: "10001")
• industry union — Industries. Example: 'SaaS' or ['SaaS', 'Cloud Computing'] (default: []; examples: "Saas")
• employee_count_min integer nullable — Min employee count. Allowed: 1, 11, 51, 101, 251, 501, 1001, 5001, 10001 (one of: 1, 11, 51, 101, 251, 501, 1001, 5001, 10001; examples: 11)
• employee_count_max integer nullable — Max employee count. Allowed: 10, 50, 100, 250, 500, 1000, 5000, 10000, 10001 (one of: 10, 50, 100, 250, 500, 1000, 5000, 10000, 10001; examples: 500)
• founded_after string nullable — Founded after date. Format: MM/DD/YYYY. Example: '01/01/2020' (examples: "01/01/2020")
• founded_before string nullable — Founded before date. Format: MM/DD/YYYY. Example: '12/31/2023' (examples: "12/31/2023")
• hiring boolean nullable — Only actively hiring companies (examples: true)
• event union — Participated in events. Example: 'Dreamforce' or ['Dreamforce', 'CES'] (default: []; examples: "CES")
• spotlight union — Diversity spotlight labels. Example: 'Black Led' or ['Black Led', 'Latine Founded'] (default: []; examples: "Black Led")
• last_funding_date_after string nullable — Last funding date after. Format: MM/DD/YYYY. Example: '01/01/2023' (examples: "01/01/2023")
• last_funding_date_before string nullable — Last funding date before. Format: MM/DD/YYYY. Example: '12/31/2024' (examples: "12/31/2024")
• last_funding_type union — Last funding round type(s) (default: []; examples: "series_a")
• last_funding_amount_min integer nullable — Min last funding amount in USD. Example: 1000000 (examples: 1000000; min: 0)
• last_funding_amount_max integer nullable — Max last funding amount in USD. Example: 50000000 (examples: 50000000; min: 0)
• funding_total_min integer nullable — Min total funding raised in USD. Example: 5000000 (examples: 5000000; min: 0)
• funding_total_max integer nullable — Max total funding raised in USD. Example: 200000000 (examples: 200000000; min: 0)
• valuation_min integer nullable — Not supported: a request that sets it returns 422. (examples: 10000000; min: 0)
• valuation_max integer nullable — Not supported: a request that sets it returns 422. (examples: 1000000000; min: 0)
• valuation_date_after string nullable — Not supported: a request that sets it returns 422. (examples: "01/01/2023")
• valuation_date_before string nullable — Not supported: a request that sets it returns 422. (examples: "12/31/2025")
• investors union — Investor names. Example: 'Sequoia Capital' or ['Sequoia Capital', 'Andreessen Horowitz'] (default: []; examples: "Sequoia Capital")
• shares_investors_with union — Companies that share investors with. Example: 'Stripe' or ['Stripe', 'Airbnb'] (default: []; examples: "Stripe")
• it_spend_min integer nullable — Not supported: a request that sets it returns 422. (examples: 500000; min: 0)
• it_spend_max integer nullable — Not supported: a request that sets it returns 422. (examples: 700000; min: 0)
• revenue_min integer nullable — Min annual revenue in USD. Allowed: 0, 1000000, 10000000, 50000000, 100000000, 500000000, 1000000000, 10000000000 (one of: 0, 1000000, 10000000, 50000000, 100000000, 500000000, 1000000000, 10000000000; examples: 10000000)
• revenue_max integer nullable — Max annual revenue in USD. Allowed: 1000000, 10000000, 50000000, 100000000, 500000000, 1000000000, 10000000000, 10000000001 (unbounded) (one of: 1000000, 10000000, 50000000, 100000000, 500000000, 1000000000, 10000000000, 10000000001; examples: 500000000)
• count integer required — Max result count (>: 0; <: 1000)

Response

• @type string (default: "CrunchbaseSearchCompany")
• id string required (format: uuid)
• name string required
• alias string required
• url string required
• cb_rank integer nullable
• logo_url string nullable
• short_description string nullable
• description string nullable
• founded_on string nullable
• employee_count_range string nullable
• categories array (default: [])
• location object nullable
  • @type string (default: "CrunchbaseLocation")
  • city string nullable
  • region string nullable
  • country string nullable
  • country_code string nullable
  • continent string nullable
  • groups array (default: [])

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.