/companies_house/companies

POST /api/companies_house/companies

Price: 20 credits

Get UK company details by registration number

How to use it

Get full details for a UK registered company by its Companies House number.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company_number string required — Company registration number (examples: "00445790")

Response

• @type string (default: "CompaniesHouseCompany")
• company_number string required
• name string required
• company_status string nullable
• company_type string nullable
• date_of_creation string nullable
• date_of_cessation string nullable
• registered_office_address object nullable
  • @type string (default: "CompaniesHouseAddress")
  • address_line_1 string nullable
  • address_line_2 string nullable
  • locality string nullable
  • postal_code string nullable
  • country string nullable
• sic_codes array
• previous_company_names array
• has_charges boolean (default: false)
• has_insolvency_history boolean (default: false)
• confirmation_statement_next_due string nullable
• accounts_next_due string nullable
• accounts_last_made_up_to 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 — Company number not found in Companies House register 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.