HTTP Ingress
The HTTP Ingress page manages HTTP-based integrations that receive pushed payloads from external systems. This is a secondary data path useful when a direct LNS integration is not possible. Because HTTP ingress receives data after deduplication at the LNS level, it provides application-level traffic visibility but not low-level RF analytics.
Key areas#
HTTP integration list#
The main view shows configured HTTP ingress integrations with each entry displaying the integration name, type, and status.
Create HTTP integration#
Click Create HTTP Integration in the top-right corner to start the creation flow:
- Select a payload decryption script — choose from available decoder scripts that match the upstream system’s payload format (e.g., Actility ThingPark).
- Name — give the integration a display name.
- Save settings — the platform allocates a unique URL and authentication token for the integration.
HTTP ingress detail view#
After creating an integration, click the eye icon to open a dialog showing the connection details you need to configure in your upstream system:
| Field | Purpose |
|---|---|
| HTTP endpoint URL | The unique URL allocated for this integration — configure this as the destination in your upstream server’s webhook or forwarding settings |
| Authentication token | The token your upstream server must include in requests for authentication |
Understanding the trade-offs#
HTTP ingress is best considered a last-resort integration path:
- Data arrives after deduplication, so the platform cannot analyze low-level gateway-level traffic.
- Only application-level traffic is visible, not individual uplink/downlink details per gateway.
- RF analysis and signal quality features are limited compared to a direct LNS integration.
It remains useful in deployments where the LNS can push data outward but does not support a deeper integration.
How to use this view#
- Navigate to Configuration > HTTP Ingress in the sidebar.
- Click Create HTTP Integration.
- Select the appropriate payload decryption script for your upstream system.
- Give the integration a name and save.
- Click the eye icon on the newly created integration to reveal the endpoint URL and authentication token.
- Copy the URL and token, then configure them in your upstream system’s webhook or forwarding settings.
Related pages#
- LNS Integrations — preferred high-quality data path
- API Ingress — API keys for external collectors
- Network — general network metadata and preferences