How it works
We move DICOM.
In. Out. Gone.
Hospitals send imaging the 1990s way. Your product speaks HTTPS. We sit in between, so you never have to run DICOM infrastructure. One API call gives you everything a sender needs:
$ curl -X POST https://api.dicomly.io/v1/endpoints \
-H "Authorization: Bearer sk_live_…" \
-d '{"name":"MGH Radiology","destination_url":"https://your-app.io/dicom"}'
# Response — everything the sender needs, in one shot
{
"id": "endpoint_01HXYZ",
"dicom_host": "dicom.yourdomain.com", // your free branded domain
"dicom_port": 11112,
"peer_ae_title": "DICOMLY", // DICOM identity — pre-configured
"certificates": [{
"id": "cert_01J5ME",
"certificate_pem": "-----BEGIN CERTIFICATE-----\n…",
"private_key_pem": "-----BEGIN EC PRIVATE KEY-----\n…" // returned once
}]
}Integration
Live DICOM in three steps
Create an endpoint
One API call returns everything: the DICOM server (dicom.yourdomain.com:11112 — your free branded domain), AE title, certificate, and private key — in a single response. Works for any DICOM source: hospital imaging system (PACS), imaging center, modality, research lab, or vendor device.
$ curl -X POST https://api.dicomly.io/v1/endpoints -H "Authorization: Bearer sk_live_…" -d '{"name":"MGH Radiology","destination_url":"https://your-app.io/dicom"}'
# → one response returns dicom_host, dicom_port, AE title, certificate + keyHand the bundle to the sender
Forward the connection details (dicom_host, dicom_port, peer_ae_title) and the certificate to whoever runs the source — a hospital PACS (imaging system) admin, an imaging-center IT manager, a research lab engineer, or a device vendor. Every value they need to enter is already in the response. Dicomly never contacts the source directly.
Receive DICOM at your webhook
Each instance arrives at your URL as a standard HTTPS POST (DICOMweb STOW-RS, the industry format for DICOM over HTTP) — any DICOM file type: X-ray, MRI, ultrasound, structured reports, waveforms. Return a standard HTTP response; Dicomly translates it back to a DICOM status for the sender — 200 means delivered, any 5xx tells the sender to retry.
POST https://your-app.io/dicom
Content-Type: multipart/related; type="application/dicom"
X-Dicomly-Endpoint-Id: endpoint_01HXYZ
X-Dicomly-Cert-Id: cert_01J5ME
# Body: raw DICOM instanceCapabilities
Everything you need to
receive DICOM
No PACS expertise required. Dicomly handles the DICOM protocol so you don't have to.
Per-device authentication
Every DICOM source is authenticated with a unique client certificate (mTLS). No shared secrets, no API keys exposed to PACS, modalities, or research devices.
Zero storage — ever
DICOM bytes flow directly from the sender to your webhook. Nothing is written to disk, a queue, or a cache — not even transiently. No PHI at rest, ever. See how we keep data secure →
One certificate per sending device
Each endpoint represents one sending facility. Within it, assign one certificate per device — scanner, PACS, workstation, archive. Revoke a single device without disrupting the others. Per-device authentication, per-facility billing and usage tracking.
Standard HTTPS delivery
Your backend receives each image as a standard HTTPS POST in DICOMweb STOW-RS format. Any DICOM file type — X-ray, MRI, ultrasound, structured reports, waveforms. Parse with any DICOM library.
Usage tracking
Per-endpoint metrics: bytes transferred, instance count, association duration. Build usage-based billing into your product from day one.
Simple REST API (standard HTTP calls — no SDK needed)
Create endpoints, issue certificates, check usage — all via a single REST API. No SDKs required. Integrates in an afternoon.
Run on your own domain (free)
Point dicom.yourdomain.com at Dicomly and hand your hospitals a DICOM address that carries your brand, not ours. One custom domain included free on every account.
Built for compliance
PHI is never stored, so there's nothing at rest to breach. EU data residency, GDPR Art. 28 DPA / BAA equivalent, and per-device certificates give you the audit trail hospitals expect — HIPAA and GDPR ready from day one.
What we carry
We don't care what's inside. If it's valid DICOM, it goes through.
- CT
- MR
- X-ray
- Mammography
- Ultrasound
- Structured reports
- RT plans
- Encapsulated PDFs
- Waveforms
Who we serve
AI & analytics startups
Stop building DICOM plumbing. Accept live data from day one without hiring a DICOM engineer or running a PACS. Add 100 sources with 100 API calls.
EHR / EMR vendors
Embed DICOM ingest into your platform without a dedicated DICOM team. Certificates map cleanly to your existing tenant model.
Teleradiology & telemedicine
Scale from dozens to hundreds of clinician-facing sites. Per-endpoint pricing maps directly to your own per-site billing model.
Research labs & academia
Ingest de-identified studies, structured reports, or RT plans from collaborating institutions. One cert per partner, revoke anytime.
OEMs & device makers
Provision connectivity at manufacturing time. Each device gets its own certificate, scoped to exactly one destination.
Imaging centers & clinics
Forward outputs from your modalities or local archive to a cloud destination of your choice — without procuring a VPN or running a DICOM router.
What we are — and what we are not
We are
- A secure pipe from the sender to your app
- Payload-agnostic: any valid DICOM goes through
- One API call per sender
- Quick to clear with your security team
We are not
- An archive or a PACS
- A viewer
- A study manager or tag-cleaning tool
- A place where patient data lives
Deliberately narrow. That's what keeps us cheap, quick to integrate, and boring to audit — in a good way.
Stateless — and why your team will like it
For security teams
Nothing to breach
No images, no patient records, no PHI backups. Nothing stored on our side to steal, ransom, leak, or wipe on request.
For on-call teams
We get paged first
We push synthetic DICOM through production 24/7, C-STORE in, STOW-RS out. Gateway trouble wakes our team, not yours.
For compliance teams
Not a custodian
A HIPAA conduit and a GDPR processor. We keep counters only — bytes, instances, timestamps. No patient IDs, no DICOM tags.
Your backend is where the data lives — we're just the pipe. See how we handle security →
Start receiving DICOM today.
Early access. No credit card. First endpoint free.