Skip to article content
API Updated 2026-06-20

Reporting telemetry to bolt-ingest

Send live device positions into Bolt with BoltReporter or another compatible tracking client.

The ingest endpoint at https://bolt-ingest.lightni.ng accepts OSMAND-style payloads. Use it when you want a client to report into one of your Bolt devices.

Authentication and identifiers

  • Every device has a Device API Token on the My Devices page. Treat it as a password.
  • Clients send that token as the device identifier (the id or deviceid field in OSMAND-style requests).
  • Keep one token per physical tracker so you can revoke or rotate credentials without affecting others.

Example request

The endpoint accepts the usual query parameters over HTTPS. Replace DEVICE_TOKEN with your Device API Token.

https://bolt-ingest.lightni.ng/?id=DEVICE_TOKEN&lat=35.1234&lon=-97.5432&speed=20&bearing=180&timestamp=2024-12-05T22:15:00Z
  • lat and lon are required; include speed, bearing, altitude, and accuracy when available.
  • Send timestamp in ISO 8601 or epoch milliseconds so Bolt can line up reports correctly.
  • HTTPS is required; unencrypted HTTP connections are rejected.

Client options

  • BoltReporter (Windows): Preloaded with the ingest URL and fields for your Device API Token. It handles reconnects and serial GPS readers automatically.
  • OSMAND-style mobile apps: Point the Server URL to https://bolt-ingest.lightni.ng, paste the Device API Token, and enable high-accuracy mode.
  • Other OSMAND-style trackers: Any tracker that speaks the OSMAND HTTP protocol can report in as long as it uses your token as the unique identifier.
Before you rely on it

Verify connectivity before rolling: confirm GPS lock, ensure the ingest domain is reachable on your network, and keep the device powered so the stream stays alive during the chase.