Add rental regulatory intelligence to your product without building the regulatory data operation behind it.
Query property-specific regulatory requirements across England, Scotland and Wales through one maintained, versioned API.
The work you don't have to run
Regulatory data is not a one-off import. Licenseye operates the discovery, collection, normalisation, review, monitoring and versioning behind the records your product consumes.
- Discovery
- Identifying the national, devolved and local sources that create rental obligations.
- Collection
- Monitoring registered authority pages, registers and documents.
- Normalisation
- Turning inconsistent source material into one record structure.
- Review
- Human approval of substantive additions and changes before publication.
- Monitoring
- Revisiting mapped sources and raising change candidates.
- Versioning
- Retaining prior versions so consumers can reconcile.
Illustrative API design
These endpoints and payloads show the intended interface and record structure rather than a published production API contract. Sample values are illustrative.
- GET
/v1/rules?uprn=100023336956Applicable requirements for a property reference - GET
/v1/properties/{uprn}/requirementsResolved requirements for a property - GET
/v1/rules?postcode=EX1%201AAApplicable requirements for a location - GET
/v1/authorities/{id}/rulesAll published records for an authority - GET
/v1/rules/{rule_id}/versionsVersion history for a record
{
"query": { "uprn": "100023336956" },
"jurisdiction": "england",
"results": [
{
"rule_id": "rul_9f3c2a",
"authority": {
"id": "auth_example_borough",
"name": "Example Borough Council"
},
"rule_type": "additional_hmo_licence",
"applicability": {
"occupiers_min": 3,
"households_min": 2,
"area": "borough_wide"
},
"obligation": "Licence required before the property is occupied as an HMO.",
"source": {
"reference": "council_policy_page",
"url": "https://example-borough.gov.uk/hmo-licensing",
"evidence": "Designation described under 'Additional licensing'."
},
"effective_from": "2025-04-01",
"reviewed_at": "2026-02-11T09:24:00Z",
"review_status": "approved",
"version": 4
}
]
}Built to be consumed, cached and audited
- jurisdiction
- England, Scotland or Wales — which framework the record belongs to.
- authority
- The body that issued or designated the requirement.
- rule_type
- A stable machine-readable category for the requirement.
- applicability
- The structured conditions under which the record applies.
- source
- Reference, URL and evidence note for the originating material.
- effective_from
- When the requirement takes effect.
- reviewed_at
- When a reviewer last approved the record.
- version
- Monotonic version of the record.
Predictable schema
Consistent field names and types across authorities.
Traceable provenance
Every result ties back to its source material.
Versioned outputs
Records carry versions so reconciliation is possible.
Change feeds
Record movements are exposed so your systems can react.
Commitments we build around
Regulatory data is only useful if integrators can trust its stability as much as its content. Coverage, cadence and commercial terms are agreed directly rather than advertised as guarantees.
Stable identifiers
Record and authority identifiers do not change underneath you.
Explicit versioning
Both the API surface and individual records carry versions.
Provenance-first outputs
Source, evidence and dates are part of the response, not an add-on.
Predictable schemas and errors
Consistent shapes and error codes so failures are handled, not guessed.
No silent record mutation
Substantive changes produce a new version rather than editing in place.
Embed rental regulatory intelligence in your product.
Talk to us about API access, response shapes, current coverage and how Licenseye data fits your existing property or compliance workflows.