Build on the CardioBridge API.
CardioBridge is infrastructure you can build on. Use the public REST API to submit ECGs, track them, and receive consultant-signed reports — then wrap it in your own product, including a fully white-label experience.
The primitives, not the plumbing.
The API gives you a small, predictable set of building blocks. You bring the product; the consultant cardiology network, the clinical governance and the EU data residency come as standard underneath.
- API keysGenerate keys in the app under Integrations and authenticate every request with an x-api-key header. Separate sandbox and production keys.
- REST APIA predictable REST API creates intakes, takes ECG files, and returns a reference you track through to a signed report.
- WebhooksSubscribe to events so your product reacts the moment a report is signed or a better trace is requested — no polling required.
- IdempotencySend your own external_id with each submission so retries are safe and every ECG maps back to a record in your system.
- EMR-inboundA universal push endpoint accepts an ECG plus patient context in a single call — the fastest way to send from another system.
- Device connectorsConnector sync brings ECGs in from devices and services in bulk, so hardware and wearables can feed the same pipeline.
Submit an ECG, get a report back.
A single request to the EMR-inbound endpoint queues an ECG for review. A GMC-registered consultant cardiologist reads and signs the report, and a webhook delivers the outcome back to you — tagged with the external_id you supplied.
No AI issues the diagnosis: the outcome in that payload comes from a named human cardiologist. Your product simply presents the result.
# Submit an ECG for consultant review — one call, your own reference
curl -X POST https://api.cardiobridge.teqdr.com/functions/v1/emr-inbound \
-H "x-api-key: <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"external_id": "YOUR-REF-123",
"email": "patient@example.com",
"dob": "1980-05-15",
"clinical_question": "Rule out AF",
"fileUrl": "https://your-system.example.com/ecg.pdf",
"fileType": "application/pdf"
}'// Webhook — a consultant cardiologist has signed the report
{
"event": "reported",
"reference": "CB-000123",
"outcome": "normal",
"letterId": "ltr_8fK29dQ",
"source": "cardiobridge"
}Your product, your brand.
Because CardioBridge is the infrastructure rather than the shopfront, what you build on top is up to you. These are examples of what the API makes possible — build any of them under your own name:
- A white-label reporting serviceWrap the API in your own brand and UX so your customers submit ECGs and receive consultant reports under your name.
- An embedded feature in your platformAdd ECG interpretation inside occupational-health, telehealth, insurance or pharmacy software your users already run.
- A device- or wearable-backed offeringPair a hardware or wearable ECG with expert review, and hand your users a signed report instead of just a raw trace.
These are patterns you can build on the platform, not pre-packaged products. Talk to us about white-label and volume terms.
Start building today.
The developer docs cover authentication, endpoints, webhooks and EMR-inbound in full — with copy-paste examples in seven languages.