HTTP Ingestion

HTTP ingestion lets any hardware able to perform a POST send measurements to Bee Thing.

Authentication

The request uses the scale token in the Authorization header.

Authorization: Bearer <scale_token>

v1 Message

The v1 message contains a message identifier and the first metrics supported by Bee Thing.

{
  "schema_version": "1",
  "message_id": "example-0001",
  "device": {
    "network": {
      "type": "wifi"
    },
    "firmware": "0.1.0",
    "hardware": "esp32"
  },
  "measurements": {
    "weight_kg": 42.3,
    "temperature_c": 18.7,
    "humidity_pct": 62.5,
    "battery_pct": 91,
    "battery_voltage_v": 4.05
  }
}

All measurements are optional, but the message must contain at least one.

Notes

The server ingestion time is the reference timestamp. Hardware does not need a reliable clock to get started.

For debugging, recently received messages are visible in the application from the Scales page, in a scale’s activity tab.

Old activity messages may be pruned regularly. Business measurements are kept.

Submissions should stay reasonably spaced. Bee Thing recommends a minimum interval of 15 minutes between two measurements sent by a scale. The service is designed for periodic field measurements, not continuous high-frequency streams.