Custom Iridium Telemetry Destinations: Email, DirectIP, and HTTPS Delivery

Getting a message over satellite is only the first step. You still need it in your database, monitoring app, or inbox. Add a custom destination in Telemetry Station and send a copy there automatically, without arranging a separate integration.

Email, DirectIP, and HTTPS API destinations are configured in the deployment details when you activate devices. Destination settings are associated with each modem IMEI and stay fixed until the devices are deactivated or the deployment end date passes.

For eligible Iridium SBD modems such as the 9602, Telemetry Station can forward supported telemetry to an email address, a DirectIP listener, or an HTTPS API endpoint. The destination configuration is submitted with the IMEI during activation and cannot be changed until the device is deactivated or its deployment ends.

DirectIP is useful when an existing application already accepts Iridium-style TCP delivery. HTTPS API delivery is often simpler for modern cloud applications because the receiving service only needs a public TLS endpoint that can accept a JSON POST request.

Certus devices such as the Iridium 9704 send messages through Iridium CloudConnect. If your software already accepts DirectIP, Telemetry Station converts those messages into a DirectIP-compatible frame before forwarding them. You can keep your existing TCP listener; this is our translation, not native Certus DirectIP.

Email and HTTPS API destinations are also available for Certus deployments. Certus device firmware must be configured with Topic ID: 394 so messages are routed to Telemetry Station and can be forwarded to your destinations.

Enter the email address that should receive your messages. The subject is Iridium message from <IMEI>, and both the plain-text and HTML versions include timestamps, the hex payload, its length in bytes, and available location details. Missing values are left blank. Messages normally come from hello@telemetrystation.com; confirm the sender with us if you use strict mail filters. Check your spam rules too: a mail server accepting a message does not guarantee it reaches your inbox.

Enter your public TCP listener as host:port or tcp://host:port; we save it with the tcp:// prefix. Use just the host and port, without login details, paths, query strings, or fragments. Private, local, and reserved addresses are not accepted. Your firewall must allow connections from Telemetry Station. See the destination documentation or contact us for the current source IP.

For both SBD and Certus, Telemetry Station writes one binary DirectIP-compatible mobile-originated frame and closes the TCP connection without waiting for an application acknowledgement. Certus uses a CloudConnect compatibility translation, not native Certus DirectIP. The message reference is iridiumDataId, not messageId. MOMSN uses a numeric messageId from 0 to 65535; null becomes zero, and out-of-range values are rejected rather than wrapped. The hexadecimal payload is decoded to raw bytes.

Configure a public https:// endpoint without embedded credentials or a fragment. Telemetry Station sends an HTTP POST with Content-Type: application/json and User-Agent: TelemetryStation-Outbound/2.0. The customer message contains an even-length hexadecimal data string, optionally prefixed with 0x, and dataLength counts decoded bytes: 48656c6c6f represents the 5 bytes of Hello. Dates are UTC ISO 8601 strings or null. Internal destination and delivery-control fields are not forwarded.

Return any HTTP 200-299 status, including 204 No Content. No response body or JSON schema is required or interpreted. Redirects are not followed. The service does not add a customer-specific Authorization or signature header; if your receiver needs a token, place it in the URL path or query. Use the destination documentation as the full integration reference.

Each custom destination costs 5 credits for each device, for each UTC calendar month the deployment touches. The fee is 5 credits × destinations × devices × calendar months. Add destinations during activation to update the quote; the activation summary and checkout include the destination charge before you pay.

For example, two destinations on 10 devices for a deployment that runs from June 20 to July 10 touches two calendar months: 5 × 2 × 10 × 2 = 200 credits. Add as many destinations as you need, or none at all. Standard dashboard, map, and API access never requires a destination.

Whether you activate as a new customer or from your dashboard, add destinations while setting up the deployment. The list applies to its devices and stays fixed until they are deactivated or the deployment ends, so check the addresses before paying.

The path is short: calculate your cost, add destinations during activation, review the updated quote, pay for credits, and activate. Telemetry Station forwards supported incoming messages to your systems while retaining paid telemetry for dashboard and API access under the service terms. Contact our team to discuss receiver design or integration help; custom engineering is not included automatically.

A delivery timeout does not always mean your receiver missed the message. Keep track of iridiumDataId so your application can recognize repeated deliveries. If you are building an HTTPS receiver, return a 2xx status; you do not need to return Telemetry Station's internal API response format. Our backend manages delivery jobs and retries; the outbound service makes one attempt per call.

Before deployment, test the receiving endpoint. For DirectIP, confirm firewall rules and listener availability. For HTTPS API, validate TLS, status-code behavior, request logging, and JSON parsing. For Email, confirm the destination mailbox accepts messages from hello@telemetrystation.com.