CRM Match
CRM contact matching and move scoring API
Put your own CRM relationships to work. Match contacts to properties, rank scored homes by move likelihood and add the brief your negotiators need. Review the run-specific price before confirming through the CSV dashboard or API.
Free account and API key. Data usage is paid; no free token allowance.
Why Homedata for CRM contact matching
Your CRM holds the relationships. Homedata gives your team the property identity, move ranking and enrichment to turn those relationships into a focused follow-up list. Address matching sits on an indexed base of 36.6M addresses; property records are keyed by UPRN, so the home behind a contact can connect to characteristics, energy evidence and market history. The CSV dashboard and CRM Match API give agencies and CRM developers two routes into the same quote, confirm and enrich workflow. A team can inspect its own matched and scored counts before authorising the run, with the scoring price visible at the point of approval.
That makes Homedata a strong choice for agencies with a contact database they want to put to work. A lead reseller supplies a new list selected by the reseller. CRM Match starts with your agency’s relationships and adds an ordering for the next conversation. Price-on-request procurement starts with a commercial quote; our scoring workflow returns a run-specific quote from your actual file, and optional enrichment can be selected separately. The real property extract on this page lets you inspect the brief a negotiator can receive, while the code sample shows exactly how to bring that process into your CRM. You can evaluate the data, the integration and the charge together.
Find the next instruction inside your existing CRM
Your agency has already done the hard work of building relationships. Past valuations, old enquiries and previous customers are a valuable starting point for the next instruction, but a long contact list gives a negotiator little guidance about where to begin. CRM Match connects the addresses you already hold to property records and move scores. You keep the relationship; Homedata adds the property context that makes the follow-up more useful.
This is a different buying decision from purchasing a fresh prospect list. Start with contacts your business already knows, review which addresses match and see how many receive a score before committing tokens. The dashboard accepts a CSV, while the CRM Match API brings the same quote, confirmation and enrichment workflow into your software. That gives an independent agency a practical upload route and gives a CRM developer a documented integration route, without requiring both teams to adopt the same operating process.
Separate address matching from paid move scoring
A contact record contains a person and an address. Only addresses go to the resolver; names, emails and phones are rejoined within the request. Matching runs on home.co.uk, where the move scores live, while the Homedata API handles the wallet billing workflow. The result preserves the distinction between a matched home, a scored home and an address that could not be resolved.
That distinction matters commercially. Unmatched contacts and matched contacts without a score are not charged for scoring. Multiple contacts at the same property are deduplicated, with the first contact retained. A large export is therefore not automatically a large scoring bill. Review the returned counts and price, then confirm the exact file and mapping. The API accepts up to 2,000 rows and 2,000,000 characters per upload, so you can split a larger CRM export into deliberate batches.
Worked output
Property enrichment for a prepared valuation conversation
Source: captured property-complete response, 30 September 2026.
CRM Match API
Quote first. Confirm the accepted charge.
Run the first request to inspect counts and price. Execute the confirmation only after the customer accepts that specific quote. The API uses your organisation’s token wallet, without a session or CSRF token.
Keep the same confirmation body and run ID when retrying a lost response. Follow the documented 503 recovery rules; successful enrichment retries are new paid calls.
import requests
url = "https://homedata.co.uk/api/v1/crm-match/match"
headers = {"Authorization": "Api-Key YOUR_KEY"}
# Replace this address-only example with your own lawful CRM export.
body = {"csv": "address\n63 Harvey Lane Norwich NR7 0AG"}
response = requests.post(url, headers=headers, json=body, timeout=60)
response.raise_for_status()
quote = response.json()
print(quote) # Inspect counts and price before approving.
# Run only after the customer accepts this quote.
if quote.get("pending_payment") and input("Accept this quote? Type CONFIRM: ") == "CONFIRM":
confirmation = {
**body,
"run_id": quote["run_id"],
"max_tokens": quote["price"],
}
paid = requests.post(url, headers=headers,
json=confirmation, timeout=60)
paid.raise_for_status()
result = paid.json()
# A changed/expired quote needs fresh approval, not an automatic retry.
if result.get("pending_payment"):
print("Review the new quote", result)
else:
print(result["contacts"])
Pricing
Review the charge before you pay
Match and score
1 token per scored contact. Unmatched and matched-but-unscored contacts are not charged for scoring.
Optional enrichment
Choose property packs or individual fields separately. Review the displayed price before confirming.
Give negotiators a useful property brief
Move likelihood helps order the work. Property enrichment helps prepare the conversation. Add bedrooms, property type, floor area or the latest recorded sale when those fields support the purpose of the call. An agency discussing a potential valuation might want the property’s sale context; a team checking the suitability of a family home might start with size and type.
The worked record below gives a negotiator a concrete property brief: 63 Harvey Lane, Norwich, is recorded as a semi-detached home with 4 bedrooms and 145 square metres of floor area. Its EPC is D, with potential C, assessed on 16 June 2015. The capture date is 30 September 2026. A team preparing a valuation conversation can bring those characteristics into its CRM alongside the separately returned move score, giving the follow-up both a priority and a useful property context.
Integrate quote, confirm and enrich through the API
Use the CRM Match endpoint on homedata.co.uk with Authorization: Api-Key YOUR_KEY. The quote request contains a CSV string and, where necessary, a mapping of zero-based column indices. The response gives submitted, matched, scored, unscored and unmatched counts alongside the price. A pending_payment response includes a run_id. Display that quote to the person authorising the work before posting the same CSV and mapping with the run ID and the accepted max_tokens value.
A quote lasts 30 minutes and is bound to the file, mapping and organisation. If the quote expires, the inputs change or the price exceeds the accepted ceiling, the service returns a new quote for review. After confirmation, matches provides the hottest-first preview, while contacts includes every matched property, including rows with a null score. Preserve that null state in your CRM. It means the home was matched without a score, so the team can still review its property context without presenting an invented ranking.
Build retries that protect the customer’s wallet
If a confirmation response is lost, retry the same request body and run ID. Confirmation debits are idempotent. A 503 response with unconfirmed:true means the debit may already have landed, so retrying the same confirmation is the appropriate recovery. A response with charged:false means no debit occurred. These are useful integration details because the customer’s billing state should stay clear even when an upstream service is temporarily unavailable.
Enrichment uses sealed contact tokens returned after matching. Send up to ten tokens per batch with a pack tier or selected fields. The tokens expire after 120 minutes and are bound to the organisation. Keep successful rows when a batch contains mixed outcomes and stop submitting more batches when out_of_tokens is returned. Successful enrichment retries are new paid property calls, unlike idempotent scoring confirmation. Your application should make that difference explicit in its retry logic and in the customer’s activity history.
A clear alternative to price-on-request procurement
For a price-on-request provider, your team needs a quote before it can compare the proposed contract with its actual contact volume. Homedata publishes token pricing and quotes the scoring run before confirmation. That makes it straightforward to evaluate a real CRM export, count usable results and decide whether further enrichment is worthwhile.
For software teams, compare the integration as well as the commercial terms. Can you inspect authentication and response fields before a sales meeting? Can you set an accepted spending ceiling? How are unresolved contacts handled? Are property packs optional? Homedata documents these behaviours and offers a free account and API key, with paid data usage through the token wallet. This is a concrete advantage for teams that want to test the workflow with their own data before planning a wider rollout.
Launch with one team and a measurable follow-up process
Choose a manageable export with complete addresses and an agreed reason for contacting the people in it. Check the mapping, review matched and unmatched counts, then approve the scoring charge. Give negotiators a short list with the relevant property context and record what happens next: conversations, valuation appointments and instructions. Measuring those outcomes against your own follow-up process is more useful than treating a likelihood score as a promise of a future move. A score prioritises attention; your relationship and service turn it into a commercial opportunity.
Uploads and results are never stored by this workflow, and API responses use Cache-Control: no-store. Your application still needs to handle its own exports and returned records appropriately. Start with scoring, add only the property fields the team will use, and review the results before scaling. You get a practical route from an existing CRM to an evidence-led call list, with the charge visible before the work is confirmed.
Start here
Evaluate the workflow on your terms
Published prices
100 tokens = £1. Review endpoint and product charges for the fields your team needs. Some standalone products are arranged per customer.
Documented integration
Inspect authentication, request inputs and returned evidence before planning your rollout.
Try the product
Explore the public API examples before signing up. Live paid calls use your wallet balance.
How much does CRM contact matching cost?
Matching and move scoring is quoted from your own CSV before confirmation. The configured scoring price is 1 token per scored contact. Unmatched and matched-but-unscored contacts are free for scoring. Optional property fields or packs are priced separately; 100 tokens equal £1.
How is CRM Match different from buying estate agent leads?
CRM Match starts with contacts your agency already knows. Address matching connects them to properties, move scores prioritise follow-up, and enrichment prepares the property brief. You retain control of your relationships and campaign instead of beginning with a reseller-selected prospect list.
Can I integrate contact matching into my CRM?
Yes. Use the documented CRM Match API to quote, confirm and enrich from your code. It supports API-key authentication, run-specific price confirmation and optional individual fields or property packs. The Python example on this page shows the initial request and accepted-quote confirmation.
How quickly can an agency get started?
Create a free account and use the CSV dashboard, or inspect the API documentation and generate a key for your integration. Review your export’s matched and scored counts, then authorise the displayed price. Property enrichment can follow after the team has chosen the useful fields.
What should our team check before following up?
Use your lawful contact process and existing preferences. Move scores prioritise attention; property assessments describe dated records. Uploads and results are never stored by this workflow, while your own software is responsible for handling its exports and returned data.
Explore
Property signals for your business
Home-improvement leads
Choose the moving-event window, installation territory and property segment that fit your trade. UPRN-linked characteristics and energy evidence give your team a useful campaign brief, with public self-serve prices before a sales call.
Housebuilder leads
Connect local moving activity with the homes behind your development campaign. UPRN-based characteristics, dated EPC evidence and market context give marketing and site sales a shared brief they can inspect before buying data.
Climate Risk API
Connect structured environmental hazard records to the identified property. Inspect the documented layers, real dated screening output and public per-call prices, then build the review panel your acquisition or portfolio team needs.
Valuation API
Give reviewers the estimate and the property evidence together. UPRN connects value, size, dated energy information and market context. Inspect a real range and confidence result, with self-serve prices available before a sales meeting.
Kitchen leads
Choose your showroom territory and recent moving-event window, then segment homes by type and size. Give designers the property context behind each consultation, with public prices and a real family-home output to inspect.
Solar installation leads
Connect local property research with EPC evidence and a documented solar assessment workflow. Choose the installation territory and qualification inputs your team needs, and inspect real energy output and public prices before integrating.
Glazing leads
Select recent moving events and the property groups your branch fits. Connected characteristics and dated EPC evidence prepare the glazing brief, with a real period-home example and public self-serve buying terms.
Blinds leads
Build your own local moving-home segment around fitting capacity. Property type and size prepare the consultation brief, while recent status-change dates give the campaign a clear timing rule. Inspect the real apartment output below.
Plumbing leads
Choose planned heating, bathroom or maintenance prospects around your engineers’ territory. Moving-event dates, property characteristics and dated energy evidence prepare the handover, with public prices and a real larger-home brief to inspect.
Build your next shortlist with evidence.
Public prices. Documented output. A free account to get started.