REST + webhooksOne schema, the same one the interface writes to

API & platform

Build around the same source of truth.

The endpoints operate on the objects the interface operates on: properties, contacts, deals, tenancies. There is no separate integration schema to reconcile, because there is no separate database behind it.

request
POST /v1/propertiesAuthorization: Bearer blc_live_••••7f2aContent-Type: application/json {  "address_line_1": "12 Kensington Gardens",  "postcode": "W2 4RT",  "listing_type": "sale",  "asking_price": 1250000,  "branch_id": "brn_8f21c",  "bedrooms": 3}
Workspace-scoped keys
Reviewed before they are granted.
Signed webhooks
HMAC, delivery log, 30-day replay.
Budget on every response
Not discovered at 429.
Versioned, not moved
Your integration keeps working.
request
POST /v1/propertiesAuthorization: Bearer blc_live_••••7f2aContent-Type: application/json {  "address_line_1": "12 Kensington Gardens",  "postcode": "W2 4RT",  "listing_type": "sale",  "asking_price": 1250000,  "branch_id": "brn_8f21c",  "bedrooms": 3}
response
201 Created {  "id": "prp_4c9a11e",  "status": "draft",  "created_at": "2026-08-20T09:41:02Z",  "portals": { "rightmove": "pending" }} → webhook property.created delivered (142ms)

/v1/properties

Listings, media, floor plans, portal state

/v1/contacts

Vendors, landlords, applicants, tenants

/v1/deals

Sales and lettings, milestones, offers

/v1/tenancies

Terms, deposits, certificates, renewals

/v1/appointments

Viewings, valuations, inspections

/v1/transactions

Client money, demands, reconciliation

Platform behaviour

Boring guarantees are the useful ones.

An integration is only worth building if it still works in eighteen months. These are the commitments that make that true.

Workspace-scoped keys

Credentials belong to one workspace and one branch scope. There is no global key that can read every agency on the platform.

Signed webhooks

Every event carries an HMAC signature and a delivery log, with replay available for the last 30 days.

Predictable limits

600 requests a minute per workspace, with the remaining budget returned on every response rather than discovered at 429.

Versioned, not moved

Breaking changes ship behind a new version. The one you integrated against keeps behaving the way it did.

12 Kensington Gardens

£1,250,000 · Under offer

UI
same record

GET /v1/properties/prp_4c9a11e
{
"asking_price": 1250000,
"status": "under_offer"
}

Read what the app reads

The list endpoints return the same filtered, sorted collections the interface renders, same fields, same names, same semantics.

214 applicants selected

Email allDraft with AIExport

Write in bulk, safely

Batch endpoints accept up to 500 records with per-record results, so a partial failure tells you exactly which rows to retry.

Completions by branch

£8.42m

+12%

Pulled by your warehouse nightly · /v1/reports

Reporting without scraping

Aggregate endpoints return the numbers behind the dashboards, so your BI tool does not have to reverse-engineer them.

Access is guided

We review integrations before we enable them

Not a gate for its own sake. Client money, tenancy data and right-to-rent records sit behind these endpoints, and an agency's regulatory position is partly our responsibility once we hand out a key.

Tell us the workflow

What system, what data, in which direction, and what happens if it stops.

We scope the access

Keys are issued against the narrowest object and branch scope that does the job.

Sandbox first

You build against a seeded workspace, then promote the same key configuration to live.

Platform access

Tell us what you need to connect, and why.

Discuss platform access

Others manageyour leads.We bring them.

Bloc runs the whole agency, and because it is built inside the Matchouse marketplace, vendors and landlords searching today find your branch. New instructions arrive instead of waiting to be chased.

No card required · Per branch, unlimited negotiators · UK-hosted