Widgets
Property data on your website.
No build. Paste a line of code and your page does the rest: an address search that fills in your form, property details and all, or the EPC, flood and schools under a listing.
Works on any site you can paste HTML into · billed to your token balance
Under a listing
Answer the questions buyers leave your site to ask.
Buyers open a new tab to check the EPC, the flood risk and the schools. Put them beside the photos instead. Each is one line of HTML with the property’s UPRN, and fills in for whichever home the page is showing.
The widgets
What each one shows
Mix them on one public key. Each renders as a small card in your page, in a light or dark theme to suit your site. Every time a widget loads it makes a call, billed to your token balance at API rates.
Drop-in widgets
Live: Address Autocomplete, Address Retrieve, Flood Risk, EPC Checker, Crime Stats, Demographics, Postcode Profile, Planning Applications and Nearby Schools. Limited: Broadband Coverage.
Coming: Transport Links and Council Tax Band.
How it works
How every widget works
Create a public key
In the dashboard, tick the widgets you need and the domains they may run on.
Paste the snippet
One script tag. Address fields are mapped by clicking them on your own page; property fields fill any input named after them.
It just renders
The widget calls us with the public key; the key is meaningless off your domain. Usage bills to your balance.
<div data-homedata-epc data-uprn="100090904564"></div>
<script src="https://homedata.co.uk/js/homedata-epc.js"
data-key="wt_your_public_key_here" defer></script>
| Who sees it | What it needs | |
|---|---|---|
| Widgets | Your customers, on your site | Public key + origin lock |
| Free tools | Anyone, on homedata.co.uk | Nothing |
| REST API | Your backend | API key |
| MCP server | AI agents and assistants | API key in the agent’s config |
What is a Homedata drop-in widget?
A drop-in widget is a single-line script tag plus a div that renders Homedata UK property data inside any website. The data comes from Homedata's API but the customer's real API key is never exposed in the browser: a scoped public key is used instead, bound to specific domains and tools.
What's the difference between a Homedata widget and the free tools?
The free tools at homedata.co.uk/tools are consumer-facing pages where anyone can look up a property without signing up. The widgets are developer-facing embeds that put the same data on a customer's own website: for example, an estate agent showing flood risk and EPC on every property listing.
Do I need to sign up to use a widget?
Yes: widgets require a public key, which is created from the Homedata developer dashboard after signing up. Pricing is pay as you go: 100 tokens = £1, no subscription needed. Bonus tokens with an optional monthly subscription. The script bundle and widget code itself are free to use.
How are widgets different from the Homedata REST API?
The REST API is server-to-server with an API key. Widgets are browser-side and use a public key plus origin lock. Both hit the same underlying data; widgets are the recommended path when you want to display data inside a webpage without writing backend code to proxy the API.
Which widgets are available?
Flood Risk (Environment Agency data by UPRN), EPC Checker (MHCLG energy rating by UPRN), Crime Stats (police.uk monthly counts by postcode), Nearby Schools (GIAS + Ofsted by postcode), and Council Tax (band + annual charge by UPRN, England, Scotland and Wales). Automated Valuations (sale + rent estimates) is live via the API; a drop-in valuation widget plus Demographics and others are coming soon: slots can be reserved on a public key now and will activate on launch.
Put the data on your pages.
Create a public key, paste one snippet, done. Billed to your balance at API rates.