Virtual AML checks
Create a check and Blinc-UK invites the client to verify themselves from their phone. You're told the moment they submit, and again when the outcome is in.
Open API
Anyone can integrate with Blinc-UK
Run Blinc-UK checks from inside the software your team already uses. Start checks, follow their progress and pull the results from your CRM, case-management or proptech platform — with a free sandbox to build against first.
Software vendors
CRM, case-management, referencing and proptech platforms that want to offer Blinc-UK checks to the firms they serve, without leaving their own product.
Agency groups with developers
Multi-branch firms with in-house or agency developers who want compliance woven into their own onboarding, pipeline or reporting tools.
Conveyancers and legal teams
Case-management systems that need AML and Land Registry evidence attached to the matter automatically, with the certificate stored alongside it.
What you can do
The checks your firm runs, from the software it runs on
Everything below is the same check, the same outcome and the same certificate you'd get in the Blinc-UK platform — just started and delivered wherever your team actually works.
In-person AML checks
Client in the branch? Start the check, send the images of their ID document from your own system, and receive the outcome and certificate back.
Land Registry searches
Search an address, list the titles found, and pull the official register and title plan — passed through at cost, exactly as in the platform.
Name-on-title checks
Confirm that a vendor or landlord actually appears on the Land Registry title of the property being transacted, in a single call.
Live updates, pushed to you
Register an endpoint and every status change arrives as a signed event — invited, submitted, completed, reviewed, cancelled — so nobody has to keep checking.
Certificates and reports
Fetch the branded AML certificate PDF for any completed check and store it against the transaction in your own system.
How it works
From first request to live checks in three steps
- 01
Create a test key
A company admin creates a test key under Company → API in the Blinc-UK platform. Test keys are free, fully separate from live data, and bill nothing.
- 02
Build against the sandbox
The sandbox runs the same endpoints with the same validation as live. Use the surname INSTANT to complete a check immediately, register a webhook endpoint and watch the events arrive.
- 03
Go live
Swap to a live key when you're ready. Live checks are billed exactly as they are in the platform — pay-as-you-go, with no minimum AML spend.
app.blinc-uk.com/api/v1
POST/v1/aml-checks201 Created
Authorization: Bearer blinc_live_•••••••• Idempotency-Key: 6f1c9a2e-… { "type": "virtual", "customer_type": "vendor", "first_name": "Jess", "last_name": "Hale", "email": "j.hale@example.co.uk", "ongoing_monitoring": true }
Then, when the client completes the check — pushed to your endpoint, signed:
Eventaml_check.completedDelivered
{
"type": "aml_check.completed",
"livemode": true,
"data": {
"id": "aml_2qk7…",
"status": "completed",
"result": { "outcome": "clear", "flags": [] },
"dashboard_url": "https://app.blinc-uk.com/…"
}
}Illustrative request and event, in the shape of the live API. All data is fictional.
For your developers
Built the way developers expect
No surprises, no reverse-engineering. The conventions your team already knows from the best-run APIs, applied to property compliance.
REST, with a published OpenAPI 3.1 spec
Plain JSON over HTTPS. The full specification is public, so you can browse it, test requests from the reference docs, or generate a client in your language of choice.
Simple API keys
Bearer keys, test and live, scoped to your company. A key can be limited to specific branches, and every check is recorded against the branch that ran it.
Signed webhooks
Every event is signed to the Standard Webhooks specification, so you can verify it really came from Blinc-UK before you trust it. Send a test ping to any endpoint you register.
Safe retries
Send an Idempotency-Key with any request that creates something, and a retry can never create a duplicate check — or a duplicate charge.
Versioning that never surprises you
Versions are dates, and every key is pinned to one. Breaking changes ship under a new version, no version is retired less than 12 months after the next, and a public changelog lists every change.
Honest errors, fair limits
Failures come back as structured problem details with a stable error code. Every response carries rate-limit headers, so your integration can back off before it's ever throttled.
Same pricing, whichever way you run a check
A check started through the API costs exactly what it costs in the platform. Pay-as-you-go, no minimum AML spend, Land Registry searches at cost — and it all lands on the same monthly invoice.
A sandbox that behaves like the real thing
Test keys hit the same endpoints with the same validation as live, so anything the sandbox accepts, production accepts too. Checks follow a scripted lifecycle and fire real signed events — without a single billed check.
Open API questions, answered
Who can use the Open API?
Anyone building for a Blinc-UK customer. API keys are created by a company admin under Company → API in the platform, so a firm can connect its own systems, and a software vendor can integrate on behalf of the firms it serves. If you're a vendor who wants to offer Blinc-UK checks to your users, get in touch and we'll get you set up with a sandbox.
Does using the API cost extra?
Checks started through the API are billed exactly as they are in the platform — pay-as-you-go, with no minimum AML spend and Land Registry searches passed through at cost. Test keys bill nothing.
Is there a sandbox to build against?
Yes. Test keys run against the same endpoints with the same validation as live, but make no real checks and bill nothing. Sandbox checks follow a scripted lifecycle, so you can see every event your integration needs to handle before you go live.
Will an update break our integration?
No. Every key is pinned to the API version that was current when it was created, and it stays on that version until you choose to upgrade it. Additive changes arrive for everyone; breaking changes ship under a new dated version, and no version is retired less than 12 months after the next one.
How do we know a webhook really came from Blinc-UK?
Every delivery is signed to the Standard Webhooks specification using the secret issued when you register the endpoint. Verify the signature before you act on an event, and use the test ping to confirm your endpoint is wired up correctly.
Does it work across our branches?
Yes. Every check is recorded against one of your branches. Leave the branch out and it goes to your primary branch; pass one to record it elsewhere. A key can also be restricted to a subset of branches when it's created.
Ready to connect Blinc-UK to your software?
Book a demo and we'll walk through the integration with your team — what to send, what comes back, and how to go live. Or point your developers straight at the docs.