IOT Developer Documentation

Architecture Overview

Raidon IoT provides a dual integration model for telemetry. Devices ingest telemetry through high-efficiency MQTT/TLS or HTTP endpoints. External customer applications can interact with this stream via REST Pull (on-demand API requests for real-time dashboards) or Webhook Push (instant notification dispatching each telemetry packet as it lands in the database).

You can configure API tokens and register webhooks directly in the Developer Integrations Console.

REST API: Authentication

All REST calls require an API key generated from the Developer Console (formatted as rdn_live_...). Pass this key in the X-Api-Key request header. Do not share your API secret token in client-side mobile or JavaScript applications.

HTTP HEADER SPECIFICATION

X-Api-Key: rdn_live_YOUR_ACTUAL_API_KEY

REST Endpoint: Pull Device Telemetry

Query the latest readings or slice time-series historical records for your claimed hardware at https://iot.raidon.in/api/v1/telemetry.php.

PULL TELEMETRY (CURL)

# Fetch the latest telemetry point
curl -X GET "https://iot.raidon.in/api/v1/telemetry.php?device_id=CUST-C4D8D53CA631&mode=latest" \
     -H "X-Api-Key: rdn_live_YOUR_ACTUAL_API_KEY"

# Fetch historical records (up to 500 records)
curl -X GET "https://iot.raidon.in/api/v1/telemetry.php?device_id=CUST-C4D8D53CA631&mode=history&limit=50" \
     -H "X-Api-Key: rdn_live_YOUR_ACTUAL_API_KEY"

Real-Time Webhooks (Push Integration)

When an IoT board transmits telemetry over MQTT or HTTP, Raidon processes the readings and dispatches an immediate HTTP POST request to your configured webhook endpoint. Each request contains a cryptographic signature to verify authenticity.

Headers Sent:
• Content-Type: application/json
• User-Agent: Raidon-IoT-Webhook/1.0
• X-Raidon-Signature: HMAC-SHA256 hex digest

Webhook destinations must return a 2xx HTTP status code within 2 seconds. If an endpoint fails or times out for 10 consecutive attempts, its status is automatically transitioned to paused.

INBOUND JSON PAYLOAD

{
  "event": "telemetry.recorded",
  "device_id": "CUST-C4D8D53CA631",
  "timestamp": "2026-10-18T13:30:00Z",
  "rssi": -65,
  "data": {
    "level": 82.5,
    "relay": 1,
    "temperature": 29.4
  }
}

HMAC-SHA256 Signature Verification

Verify every incoming webhook to ensure it originates from the Raidon broker and has not been altered in transit:

NODE.JS (EXPRESS) VERIFICATION

const crypto = require('crypto');

function verifyRaidonSignature(req, secret) {
  const signature = req.headers['x-raidon-signature'];
  const expected = crypto
    .createHmac('sha256', secret)
    .update(JSON.stringify(req.body))
    .digest('hex');
  return crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
}