What you’d build without Unified Endpoint
|
Maintain separate endpoints for each service
Duplicate transmissions for each workflow
Lock routing into the device |
Cloud Service
Soracom Unified Endpoint
A consolidated ingress endpoint service that lets you send device data once and redirect it to any of Soracom’s data services (Beam, Funnel, Funk, Harvest) without re-configuring devices.
Send data once and route it anywhere — no device reconfiguration required
Unified Endpoint provides a single entry point (e.g., unified.soracom.io) for your devices, and on the Soracom platform you choose which destination service receives the data (Beam, Funnel, Funk or Harvest). This avoids needing to update the device when your data-handling pipeline changes and enables simultaneous forwarding to multiple services.
Configure your device once, and switch backend services anytime
By using Unified Endpoint, your devices always point to the same ingress address, while you manage forwarding destinations in the console or via API. You can redirect to Beam for protocol conversion, Funnel for cloud service delivery, Funk for custom logic, or Harvest for storage—and can enable more than one destination per device-group to support dual-delivery or phased migration.
Why use Soracom Unified Endpoint for your project?
Simplify device configuration
Use one endpoint for all use cases instead of managing multiple addresses across your fleet.
Switch backend services easily
Redirect data to different services or enable multiple workflows without touching device firmware.
Reduce data duplication & cost
Forward once from device and distribute to multiple services, minimizing network load and simplifying operations.
How it works
One entry point for all data pipelines
Rather than configuring multiple endpoints, devices send data to a single host (unified.soracom.io or uni.soracom.io). You control where the data is directed on the platform side, saving device updates and enabling flexible routing.
Multi-destination forwarding
Unified Endpoint supports forwarding the same message to multiple destination services simultaneously (e.g., Beam + Harvest), thereby reducing duplicate data transmissions from devices and supporting parallel workflows such as analytics and storage.
Flexible response formats
When multiple destinations are enabled, Unified Endpoint offers configurable response formats—Auto (defaults), Unified, or destination-specific—allowing you to manage what the device receives as a reply with fine-grained control.
Key takeways for those that use Unified Endpoint
Faster device rollout
Use a consistent ingress endpoint across device models and deployments, reducing complexity and configuration overhead.
Adapt quickly
Redirect data flows across services or enable new workflows without revisiting devices.
Lower operational cost
Send data once per device and distribute as needed—reducing duplicate transmissions and simplifying your data pipeline.
Architecture and implementation
Unified Endpoint operates inside Soracom’s core platform. Devices connect using the unified host (unified.soracom.io), and Unified Endpoint applies the configured group-level forwarding destinations. It processes data (via Binary Parser or Orbit if applicable) and sends to Beam, Funnel, Funk or Harvest. You define the destinations in group settings; you don’t touch the device.
How Unified Endpoint works with other Soracom services
|
Unified Endpoint + Beam for protocol-rich routing
Unified Endpoint + Funnel/Funk for cloud integrations
Unified Endpoint + Harvest/Lagoon for analytics and storage |
Simplify device ingress with Soracom Unified Endpoint
Create a free Soracom Operator ID and start using a single entry point for your device data—then choose or switch between Beam, Funnel, Funk and Harvest on the backend.
Articles about Soracom Unified Endpoint
Frequently Asked Questions
What is Soracom Unified Endpoint?
It’s a consolidated data ingress service that provides one endpoint address for devices and lets you control where the data is forwarded (Beam, Funnel, Funk, Harvest).
Can data be forwarded to more than one destination?
Yes—Unified Endpoint supports multiple destinations for the same message, enabling use cases like simultaneous analytics & storage.
Are there limitations I should know about?
Yes. For example, the HTTP entry point supports only POST requests; MQTT entry point is not available; some TCP flows may be unsupported—see the Limitations section in docs.
Do devices need to use multiple addresses for different services?
No. With Unified Endpoint your device always uses the unified address; service redirection is managed on the platform side.
What protocols and entry points are supported?
TCP, UDP, HTTP, SMS, USSD (for supported plans) are entry options for Air for Cellular and Arc devices.
How is response formatted when multiple destinations are used?
You can set the Response Format to Auto, Unified, or destination-specific. When multiple services are enabled and Auto is selected, Unified Endpoint returns a composite response JSON.