READER INTEGRATION / VERSION 1
Give each reading
the right identity.
1. Set up its stream.
In your private sensor workspace, choose the QR point, measurement name, unit, expected interval and alert limits. Record the sensor model, calibration reference and limitations. Choose a live stream to receive a one-time device credential.
A shared reader can send several streams, with one scoped credential for each measurement. A credential can submit readings only; it cannot read customer records. Store it securely and rotate it if exposed. Do not place it in QR codes.
2. Send one event over HTTPS.
POST https://riptags.com/api/telemetry
Authorization: Bearer YOUR_PRIVATE_DEVICE_CREDENTIAL
Content-Type: application/json
{
"eventId": "d141f2fb-b8fc-4dc4-ab91-e0be2953b1b0",
"observedAt": "2026-11-15T12:00:00Z",
"value": 24.5,
"metric": "moisture",
"unit": "%",
"quality": "ok"
}Example only: generate a new UUID for each event and use its actual measurement time. The measurement name and unit must exactly match the configured stream. Values must be finite. Send quality “invalid” for a numerical reading that the device cannot trust; it triggers a check rather than being treated as normal.
3. Keep retries honest.
| Response | Reader behaviour |
|---|
| 201 | New event stored. Retain the returned reading ID with your acknowledgement. |
| 200, duplicate: true | The identical event was already stored. Remove it from the send queue. |
| 400 / 409 | Inspect the data, clock, unit or reused event ID. Do not disguise a retry as a new measurement. |
| 401 | Credential is missing, revoked or invalid. Stop and request configuration. |
| 429 / 503 / network failure | Keep the event in a persistent local queue. Retry with exponential backoff, using the same event ID, value and timestamp. Check capacity if 429 persists. |
Accepted observation times are within the preceding seven days, with at most 30 seconds of clock skew. Late readings remain historical evidence; they do not overwrite a newer condition. Maximum 60 readings per stream per minute. Use local sampling and summaries for high-frequency signals.
4. Verify the full loop.
- Send a baseline reading, then a controlled change across a configured limit.
- Confirm the correct point, source, observation time and receipt time.
- Check the follow-up, its effect on connected inspection priorities and the browser notification attempt.
- Record the engineer’s review and action.
- Send a fresh valid reading within the configured rules; add a human no-change check at the same point.
- Explicitly close the follow-up and export its evidence report.
Use test streams for synthetic checks. They are labelled in records and reports and cannot accept live device credentials. No physical sensor, calibration, battery life or connectivity claim is established by a software test.
Retention and missing data.
Sensor readings have a separate 200,000-record allowance per location and up to 90 days of raw retention. Export before that period expires. Alert snapshots and approved reference evidence remain in the audit record. At the allowance, intake refuses new events until capacity is available; the reader must retain its queue.
A stream is stale after three expected intervals without a valid reading. Unattended health checks and notification retries require the scheduled operations connection; the sensor workspace shows when that check last ran. A disconnected or uninstrumented point has an unknown condition.
Browser notifications require explicit opt-in and a supported browser. Push-service acceptance does not confirm receipt by a person. Email/SMS, hardware drivers and guaranteed emergency alert delivery are not included.