Send data over HTTP

Devices that cannot speak MQTT can post readings directly to the device event API. This page covers the workflow; the full contract is in the device event API reference.

Find the connection settings

For an API device, open its overview to find its access token and the Copy API URL action. Use that copied URL for your environment.

Keep the device token private and send it in the Authorization header rather than in the request body, so tokens are not mixed into telemetry payloads or written to message logs.

Request format

Send a POST request to /api/v1/deviceapi/event with Content-Type: application/json and Authorization: Bearer YOUR_DEVICE_TOKEN.

request body


{
  "serial": "YOUR_DEVICE_SERIAL",
  "data": {
    "temperature": 23.4,
    "humidity": 58
  }
}

The serial identifies the device. The keys inside data must match its configured input names.

Examples

curl


curl -X POST "https://YOUR_API_URL/api/v1/deviceapi/event" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_DEVICE_TOKEN" \
  -d '{
    "serial": "YOUR_DEVICE_SERIAL",
    "data": { "temperature": 23.4, "humidity": 58 }
  }'

Python


import os
import requests
 
response = requests.post(
    f"{os.environ['DIGISENSE_API_URL']}/api/v1/deviceapi/event",
    headers={"Authorization": f"Bearer {os.environ['DEVICE_TOKEN']}"},
    json={
        "serial": os.environ["DEVICE_SERIAL"],
        "data": {"temperature": 23.4, "humidity": 58},
    },
    timeout=10,
)
 
result = response.json()
if not result.get("success"):
    print("rejected:", result.get("message"), result.get("error"))

Node.js


const response = await fetch(
  `${process.env.DIGISENSE_API_URL}/api/v1/deviceapi/event`,
  {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Authorization: `Bearer ${process.env.DEVICE_TOKEN}`
    },
    body: JSON.stringify({
      serial: process.env.DEVICE_SERIAL,
      data: { temperature: 23.4, humidity: 58 }
    })
  }
)
 
const result = await response.json()
if (!result.success) {
  console.error('rejected:', result.message, result.error)
}

Verify the result

Inspect the response body for its success or error result:

accepted


{
  "success": true,
  "message": "Message processed and data stored successfully"
}

The response body carries the real outcome. A request can complete without a transport error and still report "success": false — for example "No connections configured" when no entity mapping exists for the keys you sent. Always read success, not just the HTTP status.

Then check the device’s Messages tab and the values of the mapped entity inputs. An accepted request and a correctly configured dashboard are separate checks.

See the reference for every response your integration should handle.