Connecting to Synura
Synura accepts HL7 v2 messages over Synura Connect (port 443) and HTTPS. Synura Connect handles the TLS connection for you — it uses MLLP over TLS under the hood, so any system that speaks MLLP can connect. How you connect depends on what you’re working with.
Which path is right for you?
Section titled “Which path is right for you?”| Your situation | Go here |
|---|---|
| I use Mirth Connect | Quick Start — automated installer, under 5 minutes |
| I use an integration engine with TLS support (Rhapsody, Iguana, InterSystems, Epic Bridges, Cloverleaf, etc.) | Synura Connect (native MLLP over TLS) — point your engine at Synura directly, no bridge software needed |
| I want to send HL7 messages via REST API | HTTPS API — POST messages to a single endpoint |
| I’m building a custom integration in code | Code Samples — working Synura Connect examples in Python, Java, C#, Node.js, and Go |
Connection details (all methods)
Section titled “Connection details (all methods)”Every Synura connection uses these values:
| Setting | Value |
|---|---|
| Host | {subdomain}.synura.io |
| Port | 443 |
| TLS | 1.2 minimum |
| Certificate | Let’s Encrypt (ISRG Root X1) |
| SNI | Required |
Your subdomain is assigned when you create an endpoint in the Synura dashboard (e.g. acmelab).
Having trouble?
Section titled “Having trouble?”- Troubleshooting — TLS Proxies and Trust Stores for enterprise network issues
- Troubleshooting for Mirth-specific problems
- Email support@synura.io with your subdomain and a description of the issue