/opencorporates/companies/search

POST /api/opencorporates/companies/search

Price: 5 credits

Search companies on OpenCorporates by name or keyword, with optional jurisdiction filter. Returns at most 250 companies per call, ranked by relevance. has_details is false for a company whose status, type, dates and address could not be loaded

How to use it

Search OpenCorporates for companies by name or keyword. Returns name, company number, jurisdiction code, status and source URL. Optionally filter by jurisdiction_code (e.g. 'gb' for United Kingdom, 'us_de' for Delaware). At most 250 companies per call; split larger sets by jurisdiction_code.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Company name or keyword to search (examples: "Apple", "Tesla"; minLength: 1)
• count integer required — Number of results to return. One query returns at most 250 companies; split a larger result set with jurisdiction_code or a narrower query (min: 1)
• jurisdiction_code string nullable — Filter by jurisdiction code, e.g. 'gb', 'us_de' (examples: "gb", "us_de")

Response

• @type string (default: "OpenCorporatesCompanyResult")
• name string required
• company_number string required
• jurisdiction_code string required
• current_status string nullable
• company_type string nullable
• incorporation_date string nullable
• dissolution_date string nullable
• registered_address string nullable
• is_branch boolean (default: false)
• has_details boolean (default: true)
• source_url string required

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.