Download Iridium telemetry from the dashboard or your own workflow.
Select devices, define a UTC date range, and export retained telemetry as JSON or CSV. The dashboard builds the same authenticated URL shown in this documentation.
*While the account remains active and in good standing, subject to the Terms, technical limits, and account status.
The real endpoint and profile key are supplied inside the authenticated dashboard. Never publish or commit a live key.
From authenticated account to exported telemetry in four steps.
The normal customer path requires no hand-built request. The dashboard validates the fields and creates the URL for you.
Open the dashboard
Sign in to the Telemetry Station account that owns the devices and telemetry records.
Select devices
Choose individual device rows, select the entire fleet, or leave every row clear to include all available devices.
Choose UTC dates
Set a start day, an end day later than the start, and choose JSON or CSV output.
Download or integrate
Open the generated URL for a direct file download or copy it into an authenticated server-side workflow.
Explore the real dashboard download workflow with safe example data.
Change the selected devices, UTC range, output format, and code language. All IMEIs, telemetry values, and credentials below are fictional.
Select devices and export telemetry.
This is the same selection and download workflow used in the authenticated dashboard, populated with fictional devices and illustrative telemetry. If no devices are selected, all devices are included.
Export dates are UTC calendar days. The generated API URL sends the selected start and end dates as midnight UTC ISO strings.
curl --fail --location "{DATA_DOWNLOAD_API_URL}/?apiKey=YOUR_API_KEY&imeis=300000000000001%2C300000000000002%2C300000000000003&start=2026-08-14T00%3A00%3A00.000Z&end=2026-08-21T00%3A00%3A00.000Z&format=json" --output telemetry.json[
{
"imei": "300000000000001",
"deviceName": "North Pacific Buoy",
"messageTimeUtc": "2026-08-14T08:00:00.000Z",
"network": "sbd",
"latitude": 32.87051,
"longitude": -117.24103,
"payloadHex": "016a8f2c4d09",
"payloadBytes": 6
},
{
"imei": "300000000000002",
"deviceName": "Coastal Weather Station",
"messageTimeUtc": "2026-08-14T11:00:00.000Z",
"network": "sbd",
"latitude": 33.05483,
"longitude": -117.46817,
"payloadHex": "0191b72d510c",
"payloadBytes": 6
},
{
"imei": "300000000000003",
"deviceName": "Research Drifter",
"messageTimeUtc": "2026-08-14T14:00:00.000Z",
"network": "certus",
"latitude": 33.23915,
"longitude": -117.69531,
"payloadHex": "0a4f19c00173e82b5d",
"payloadBytes": 9
}
]
One authenticated GET request.
Use the exact base URL generated by the dashboard. The export builder appends these five query parameters in the order shown.
The current dashboard reads the API key from the authenticated profile and places it in the generated query string. Use HTTPS, keep the full URL private, and rotate the key if it is exposed.
apiKeyThe API key associated with the authenticated Telemetry Station profile.
imeisOne or more 15-digit device IMEIs separated by commas. Duplicate values are removed by the dashboard builder.
startThe selected start calendar day converted to midnight UTC.
endThe selected end calendar day converted to midnight UTC. It must be later than start.
formatThe requested download representation.
Understand the exported records
JSON preserves structured values for application integration. CSV is convenient for spreadsheets and offline analysis. The exact decoded fields depend on the device and parser configured for the deployment.
The 15-digit Iridium device identifier associated with the message.
The customer-facing device name and related device metadata when available.
The message or observation time represented in UTC. Keep this timezone when storing or comparing records.
The applicable Iridium SBD or Certus context and related message metadata when available.
Raw payload bytes or hexadecimal representation, depending on the export and device integration.
Sensor-specific fields when a decoder is configured. Field names and units vary by device and integration.
Validate before requesting
The dashboard blocks invalid export URLs before opening a download. A server integration should perform the same checks and treat every non-successful HTTP response as a failed export.
Protect access and preserve the source data.
Keep keys server-side
Do not place a live API key in a public repository, browser bundle, screenshot, ticket, or shared document.
Normalize timestamps
Treat request dates and returned timestamps as UTC, then convert only at the presentation boundary.
Maintain exports
Customers remain responsible for the backups and exports required by their own retention and recovery policies.
Handle integration changes
Validate responses, preserve error bodies for troubleshooting, and follow communicated access or usage limits.
Sign in to generate a live telemetry download.
Need a custom decoder, private-data workflow, fleet migration, or direct technical review? Contact the Telemetry Station and Pacific Gyre engineering team.