Connect via HTTP Ingress

This guide explains how to set up an HTTP ingress integration in Canopy NOC. HTTP ingress accepts pushed payloads from external systems via webhook, making it useful when a direct LNS integration is not available.

HTTP ingress is a secondary data path. Because data arrives after deduplication at the LNS level, the platform receives only application-level traffic. Low-level RF analytics such as per-gateway signal quality, spreading factor distributions, and multi-gateway correlation are not available through this method. Use a direct LNS integration whenever possible.

Before you begin#

  • Confirm you have an active Canopy NOC account with permission to manage integrations.
  • Have administrator access to the upstream system (e.g., Actility ThingPark) that will push payloads to Canopy NOC.
  • Know which payload format your upstream system uses so you can select the correct decoder script.

Step 1 – Create the HTTP ingress#

  1. Open the sidebar and navigate to Configuration > HTTP Ingress.
  2. Click Create HTTP Integration in the top-right corner.

Create HTTP Integration dialog

  1. Select the payload decryption script that matches your upstream system’s format (e.g., Actility ThingPark).
  2. Enter a descriptive Name for this integration.
  3. Click Save.

Step 2 – Retrieve the endpoint URL and token#

After saving, the platform generates a unique endpoint URL and authentication token for this integration.

  1. In the HTTP Ingress list, click the eye icon on the integration you just created.
  2. Copy the HTTP endpoint URL and the authentication token from the detail dialog.

HTTP Ingress detail showing endpoint URL and token

Store the authentication token securely. You will need both the URL and the token to configure the upstream system.

Step 3 – Configure the upstream system#

In your upstream platform (e.g., Actility ThingPark), set up a webhook or forwarding rule that sends payloads to the Canopy NOC endpoint.

  1. Open the webhook or HTTP forwarding configuration in your upstream system.
  2. Set the destination URL to the endpoint URL copied in Step 2.
  3. Add the authentication token as required by the upstream system (typically as a header or query parameter).
  4. Save and activate the forwarding rule.

Step 4 – Verify data flow#

  1. Return to Configuration > HTTP Ingress in Canopy NOC.
  2. Click the eye icon on your integration.
  3. Confirm that the Last activity timestamp updates and that metrics show incoming data.

What to do next#

Updated on 05 May 2026