Receive DICOM
from anywhere.
Any software team can receive live DICOM data — from hospitals, imaging centers, clinics, research labs, or device vendors. No DICOM engineers, no infrastructure, no PACS. One API call provisions a mTLS certificate. Bytes flow directly to your webhook in real time. Dicomly never stores, buffers, or inspects the payload — it is a pipe, not a custodian.
$ 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": "ep_01HXYZ",
"dicom_host": "dicom.dicomly.io",
"dicom_port": 11112,
"peer_ae_title": "DICOMLY",
"certificate_pem": "-----BEGIN CERTIFICATE-----\n…",
"private_key_pem": "-----BEGIN EC PRIVATE KEY-----\n…"
}How it works
Everything you need to
receive DICOM
No PACS expertise required. Dicomly handles the DICOM protocol so you don't have to.
mTLS authentication
Every DICOM source is authenticated with a unique client certificate. No shared secrets, no API keys exposed to PACS, modalities, or research devices.
Pure pipe — zero storage
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. This makes Dicomly a HIPAA conduit, not a Business Associate custodian, and a GDPR processor, not a data host.
One cert per site
Each endpoint can hold many certificates — one per sending site or device. Revoke a single source without affecting the others. Fan-in, never fan-out.
STOW-RS delivery
DICOM instances arrive at your HTTPS endpoint as standard DICOMweb STOW-RS multipart requests. Any SOP class — images, SR, RT, PR, 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
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
Create an endpoint
One POST /v1/endpoints call returns everything:
the DICOM server (dicom.dicomly.io:11112), AE title, certificate,
and private key — in a single response. Works for any DICOM source: hospital 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 'dicom_config' + cert to the sender. That's it.
{
"id": "ep_01HXYZ",
"dicom_host": "dicom.dicomly.io",
"dicom_port": 11112,
"peer_ae_title": "DICOMLY",
"dicom_config": { "host": "dicom.dicomly.io", "port": 11112, "called_ae_title": "DICOMLY", "tls": true },
"certificate_pem": "-----BEGIN CERTIFICATE-----
…",
"private_key_pem": "-----BEGIN EC PRIVATE KEY-----
…"
}Hand the bundle to the sender
Forward the dicom_config block and the certificate to whoever
runs the source — a hospital PACS 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
DICOM instances arrive at your URL as standard STOW-RS multipart/related
HTTP POST requests — any SOP class (images, SR, RT, PR, waveforms).
Map the response code to a DIMSE status: 200 means success,
5xx tells the sender to retry.
POST https://your-app.io/dicom
Content-Type: multipart/related; type="application/dicom"
X-Dicomly-Endpoint-Id: ep_01HXYZ
X-Dicomly-Cert-Fingerprint: a3:b1:…
# Body: raw DICOM instancePricing
Start free. Pay as you grow.
Per endpoint
One connected DICOM source. Prorated by the second.
Egress
Bytes delivered to your STOW-RS receiver. Inbound from hospitals is free.
First endpoint
Forever — for evaluation and CI. No credit card required.
Start receiving DICOM today.
Early access. No credit card. First endpoint free.