Early Access
Request early access
DICOM API connectivity

Receive DICOM
from anywhere.

Hospitals, clinics, labs, device vendors — one API call and the bytes land on your webhook. No DICOM engineers. No PACS. No storage. Just live imaging data, streamed straight to you.

Request early accessRead the docs

Production DICOM since 2010 — tech team behind a Philips-acquired platform →

Create an endpoint
$ 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": "relay.dicomly.io",
  "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
  }]
}

Why Dicomly

Storage is the easy part.
Receiving DICOM is the hard part.

Cloud archives answer "where do we keep the images?" — but only after the images have already arrived somewhere. Getting them off a hospital's scanner, over the wire, and into your app is the part nobody hands you. That's the part Dicomly does.

Hospital scanner

PACS · modality · archive

The hard part

DICOM protocol · mTLS · provisioning

Dicomly

Your app

store it anywhere you like

Object storage is great at keeping a recording of a phone call — but it has nothing to do with receiving the call from the carrier. Dicomly is the carrier side of medical imaging: it receives the DICOM, then hands you the bytes over plain HTTPS. Keep them wherever you want.

See how Dicomly compares to storage, PACS, and on-prem routers

Capabilities

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.

Integration

Live DICOM in three steps

01

Create an endpoint

One API call returns everything: the DICOM server (relay.dicomly.io:11112), 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"}'

# Response — hand the connection details + cert to the sender. That's it.
{
  "id": "endpoint_01HXYZ",
  "dicom_host": "relay.dicomly.io",
  "dicom_port": 11112,
  "peer_ae_title": "DICOMLY",
  "certificates": [{
    "id": "cert_01J5ME",
    "certificate_pem": "-----BEGIN CERTIFICATE-----\n…",
    "private_key_pem": "-----BEGIN EC PRIVATE KEY-----\n…"
  }]
}
02

Hand 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.

03

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 instance

Built for teams receiving DICOM

Pricing

Start free. Pay as you grow.

Per endpoint

€10/ month

One connected DICOM source. Prorated by the second.

Egress

€0.15/ GB

Bytes delivered to your HTTPS receiver (DICOMweb STOW-RS). Inbound from hospitals is free.

FreeFirst endpoint is free, forever — no credit card.
Plus a €5 signup credit (~30 GB egress) to wire up a real integration. After that, egress is €0.15/GB; inbound from senders is always free.
Request early accessEnterprise (1 000+ endpoints)
See full pricing details

Start receiving DICOM today.

Early access. No credit card. First endpoint free.

Request early accessRead the quickstart