Release Version: BetaRelease VersionBeta

Setup

Prerequisites

Before setting up this integration, make sure you have:

  • A Monnit credential with a valid API Key ID and API Secret Key
  • Access to the Monnit Network ID and Sensor ID you want to connect
  • A Monnit credential HTTP ingress endpoint configured for pushed data
  • An iMonnit webhook configured to send data to the credential’s HTTP ingress endpoint

Credential Setup

Use Monnit Credentials to create or select the credential for this integration.

The Monnit credential stores the API authentication details and can include a credential-level HTTP ingress endpoint. Monnit source integrations using that credential inherit the endpoint.

If you still need to create Monnit API keys, use Monnit’s iMonnit REST API Authentication guide.

The iMonnit webhook must be configured during credential setup for pushed data to reach IMSURGE.

Integration Setup

After selecting the Monnit credential, configure the source using:

  • Network ID - The Monnit network that contains the sensor you want to connect. This is selected from networks fetched through the credential.
  • Sensor ID - The Monnit sensor IMSURGE should use for this source integration. This list is loaded after Network ID is selected.

IMSURGE automatically looks up the Application ID from Monnit using the selected sensor. Users do not manually fill in Application ID.

Reference

Credential fields are documented in Monnit Credentials.

Field Description Required
Network ID The Monnit network selected from networks fetched through the credential. Setup Only
Sensor ID The Monnit sensor selected from sensors in the chosen network. ✓
Application ID Internal value automatically fetched from Monnit using the selected Sensor ID. Users do not manually fill this in. Derived

This integration uses Data Push.

Monnit pushes data to the HTTP ingress endpoint attached to the Monnit credential. Any Monnit source integrations using that credential inherit the endpoint.

When Monnit pushes data to the credential endpoint, IMSURGE uses the incoming message details to route the data to the appropriate Monnit source integration.

Configure this endpoint in iMonnit as a webhook destination. See Monnit’s Configuring an iMonnit Webhook guide.

This integration supports Manual Execution for recent historical data. Monnit does not use a polling schedule, so it does not have a Default mode execution option.

Execution Type Data Range
Backtrack Up to 7 days

Limitations

  • Credential-level ingress endpoint - The HTTP ingress endpoint belongs to the Monnit credential, not the individual source integration. Integrations using the same credential inherit the same endpoint.
  • Application ID is derived - IMSURGE fetches the Application ID automatically from Monnit using the selected Sensor ID. Users do not manually set or edit it.
  • Beta Integration - Monnit is a beta integration. Results may vary while the integration is being validated.

External References