Skip to content

Corporate property data and current API scope

UK Company Property Data: API Scope

Understand the HM Land Registry corporate ownership source policy alongside the property fields currently declared in the public API.

Claim your keyRead the quickstart

What it makes possible

A public-record check that keeps its provenance

Rotuli's source policy describes HM Land Registry's UK Companies that Own Property dataset (CCOD). The current public OpenAPI document does not declare a land source in sources_checked or a land_holdings property in the entity response, so an integration must not assume those fields are available from the published contract.

01

Check the published response before integrating

Start with the entity schema rather than the source description. The currently declared entity response contains company, PSC, insolvency, charge, and officer slabs; it does not declare a property slab or property query endpoint.

02

Keep CCOD facts separate from delivery scope

The source policy describes title number, tenure, a registered price where available, and postcode-only addresses. Those are source-policy facts, not fields a caller can rely on until the API schema exposes them.

03

Apply the source boundaries when support is published

CCOD covers registered corporate titles in England and Wales. Scotland and Northern Ireland use separate land registries. The source policy also limits redistributed addresses to postcode-only or null because full addresses cannot be redistributed through this API.

Response surface

Fields to put in the workflow

The response uses named slabs, stable enum values, and null or empty values instead of silently omitting fields.

Published entity schema
Does not currently declare a land_holdings property or a land source in sources_checked.
CCOD source policy
Describes corporate title records for England and Wales, with tenure and a price paid where the source recorded one.
Property search endpoint
Is not declared in the current published OpenAPI document.
Address handling
The source policy limits any future redistributed address field to a postcode or null.

Interpretation

Property data is a title record, not a valuation

CCOD data would support questions about recorded corporate ownership, tenure, and a historic registered price where present; it would not establish market value, complete beneficial ownership, or coverage outside England and Wales. Until the public contract exposes a property field, use the current schema rather than treating the source-policy description as an integration guarantee.

Review prompts

  • Does the deployed schema expose a property field needed by this workflow?
  • If property support is published, which title and tenure records are in scope?
  • Is a registered price appropriate to use as historic context only?
  • Does the use case require a geography or property detail CCOD does not cover?

First request

Start with a company number

curl "https://api.rotuli.co.uk/v1/entity/00445790" \
  -H "Authorization: Bearer uk_live_YOUR_KEY"

The Free tier includes 500 requests per month with no card required. See the API reference for the full response schema and data sources for licence and freshness details.

Guide: map UK registry fields into your product