How to connect an HTTP data source to Infodeck

Use HTTP webhook when your external system can send sensor readings in Infodeck's supported message format. This requires an integration administrator who can configure the sending system and match its data to an Asset Type decoder.

Quick summary: Create the connector, register the receiving asset, send an authenticated JSON message containing assetId and payload, then confirm the actual measurements.

Before you begin

You need:

• Permission to view, create and update integrations, and to register assets in the relevant location.
• An external system that can send HTTP POST requests with JSON and an Authorization header.
• An IoT Asset Type with a decoder and measurement fields matching the incoming data.
• The external system's outbound command destination and credential if commands are required.

Incoming readings and outgoing commands

The copied Webhook URL and Authorization receive readings in Infodeck. Host and API key configure commands sent from Infodeck to the external system. The current editor requires both command fields to finish setup. For an incoming-only installation, ask Infodeck Support to confirm the configuration before proceeding; do not enter invented values.

1. Create the connector

1. Open Settings → Integrations.
2. Click Add connector, select Automation, then choose HTTP webhook.
3. Enter a Connector name, such as Building data bridge.
4. Add a Description if helpful, then click Create and continue.
5. In Complete connector setup, enter the agreed Host and API key.
6. Click Save changes.

Creating the record does not configure the sending system or prove that it can exchange data.

2. Copy the incoming connection details

1. Open the connector and click Edit connector.
2. Under Provider webhook, use Copy webhook URL for the sender's destination.
3. Use Copy authorization for the sender's Authorization header.

Use the complete copied authorization value without adding another prefix. Keep it confidential. It is separate from the API key entered for outbound commands.

Connector field reference

Field	Required	What it means
Connector name	Yes	Recognizable name, up to 256 characters.
Description	No	Optional context, up to 1,000 characters.
Webhook URL	Copy from Infodeck	Destination for incoming sensor messages.
Authorization	Copy from Infodeck	Value for the incoming request's Authorization header.
Host	Yes in the editor	External destination for outgoing command requests.
API key	Yes in the editor	External credential used for outgoing commands.

3. Register the receiving asset

1. Open Assets and start registering an asset.
2. Select the matching Asset Type and enter an Asset Name, such as Plant room temperature.
3. Select your HTTP connector in Integration Service.
4. Enter the agreed Device UUID, select the Location, then click Register Asset.
5. Obtain the saved asset's Infodeck asset ID for the sending system. Ask your administrator if needed.

The asset ID in the HTTP message must identify this existing Infodeck asset in the same workspace. Do not substitute its display name or assume an external device ID is the Infodeck asset ID.

4. Configure the incoming message

Configure the external system to POST JSON to the copied Webhook URL, using Content-Type: application/json and the copied Authorization header.

The body has this structure. Replace the explanatory asset-ID placeholder with the saved asset's ID:

{
  "assetId": "REPLACE_WITH_INFODECK_ASSET_ID",
  "payload": {
    "temperature": 23.5
  }
}

Body field	Required	Supported value
assetId	Yes	The existing Infodeck asset ID.
payload	Yes	A JSON object or array of objects in the format expected by the Asset Type decoder.

temperature is an example agreed with your decoder, not a universal measurement field. The incoming handler provides the decoder with the received body, its payload as data, and a receipt timestamp. Ask the person configuring the decoder to account for this structure and any source timestamps.

caution

This connector does not accept every provider's webhook format automatically. If the sender produces a different structure, your integration administrator must transform it before delivery and configure the matching decoder.

5. Confirm a real reading

1. Send one known measurement from the external system.
2. Check the response body as well as the HTTP status. forwarded: false means forwarding failed, even if the status is successful.
3. Open the asset in Infodeck and check its current measurements and Reading history.
4. Compare the value, unit and report time with the reading you sent.

Even forwarded: true does not prove useful measurements were stored. A decoder or measurement mapping can still produce no readings. Verify the asset before sending the full data stream.

Change settings later

Open Settings → Integrations → your connector → Edit connector, make the changes and click Save changes. Leaving an existing masked API key blank keeps its stored value. Changing Host or API key does not change the sender's webhook settings.

Troubleshooting

What you see	What to check
Setup asks for Host and API key	These are required by the current editor. Confirm the outbound configuration with Support, especially for incoming-only use.
Authorization fails	Copy the complete Authorization value from the correct connector into the sender's header.
forwarded: false	Check the body, asset ID, workspace and decoder configuration.
Success response but no measurements	Confirm the decoder understands the wrapper and measurement fields; inspect actual asset history.
Incoming readings work but commands fail	Check Host, API key and the separately configured command action with your administrator.

Example: plant room temperature

Create Building data bridge and register Plant room temperature with its agreed decoder. Send a test value of 23.5 using the saved asset ID. Confirm the displayed unit is correct and a new history entry appears before enabling regular transmission.

Related guides

• Register an asset
• Asset Types
• Sensor data
• Integrations & Connectors

Need help matching the sender and decoder? Contact Infodeck Support.