/owler/companies/search

POST /api/owler/companies/search

Price: 1 credit

Search Owler (owler.com) companies by sector, location, type, revenue and employee filters

How to use it

Search Owler (owler.com) companies by industry sector, headquarters location, company type, annual revenue range and employee-count range. Returns matching companies with name, alias, description, CEO and follower count. Use the returned alias with /owler/companies for the full profile.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• sector array — Filter by one or more industry sectors (default: []; one of: "Aerospace & Defense", "Agriculture, Forestry & Paper", "Automobiles & Parts", "Banking, Financial Services and Insurance", "Chemicals, Metals & Mining", "Education", "Energy & Utilities", "Food & Beverages", "Health Care Equipment & Services", "Industrial Goods & Services", "Manufacturing", "Media, Entertainment and Arts", "Non-Profit & Government", "Personal & Household Goods", "Pharmaceuticals & Biotechnology", "Professional Services", "Real Estate & Construction", "Retail", "Software, Internet & Computer Services", "Technology Hardware & Equipment", "Telecommunications", "Transportation, Warehousing & Logistics", "Travel, Recreation & Leisure"; examples: ["Software, Internet & Computer Services"])
• company_type array — Filter by one or more company types (default: []; one of: "Private", "Public", "Product/Brand/Service", "Investment Company", "Government", "NGO/NPO/NFP/Organization/Association", "SPAC"; examples: ["Public"])
• location array — Filter by one or more headquarters locations (city, region or country names) (default: []; examples: ["California","Boston"])
• revenue_min integer nullable — Minimum annual revenue in USD (examples: 10000000; min: 0)
• revenue_max integer nullable — Maximum annual revenue in USD (examples: 1000000000; min: 0)
• employees_min integer nullable — Minimum employee count (examples: 100; min: 0)
• employees_max integer nullable — Maximum employee count (examples: 10000; min: 0)
• founded_on integer nullable — Founded exactly in this year (examples: 2010; min: 1600)
• founded_before integer nullable — Founded before this year (examples: 2010; min: 1600)
• founded_after integer nullable — Founded after this year (examples: 2010; min: 1600)
• count integer required — Max number of results to return (min: 1; max: 8)

Response

• @type string (default: "OwlerSearchCompany")
• id integer required
• name string required
• alias string nullable
• url string nullable
• description string nullable
• image string nullable
• follower_count integer nullable
• ceo_name string nullable
• ceo_title string nullable
• ceo_image 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.