Web APILive Pings
Live Pings
Server-sent event streams of pings as they arrive and as they finish processing.
https://api.staging.locantra.deStream processed pings as they are finished
https://api.staging.locantra.de/live/pings/processedStreams your organisation's pings once the platform has enriched them with their transponder assignment, order, geofence and resolved position — the same shape the ping endpoints return, delivered live. The response is a server-sent event stream: one `data:` frame per ping, as JSON, with a `: keepalive` comment every 15 seconds to hold the connection open. Frames carry no event name and no id, so a dropped connection resumes at the present, not where it left off. DeviceID and TransponderID narrow the stream; repeat a parameter or pass a comma-separated list, and a ping is delivered when it matches at least one value of every filter that is set. OrderID and GeoFenceID filter this stream as well. An organisation may hold 50 live-ping connections at once, counted across the raw and the processed stream together; the 51st is refused with 429.
Stream raw pings as they arrive
https://api.staging.locantra.de/live/pings/rawStreams your organisation's pings the moment they are received, before the platform resolves the transponder assignment, order or geofence behind them — the lowest-latency view there is. The response is a server-sent event stream: one `data:` frame per ping, as JSON, with a `: keepalive` comment every 15 seconds to hold the connection open. Frames carry no event name and no id, so a dropped connection resumes at the present, not where it left off. DeviceID and TransponderID narrow the stream; repeat a parameter or pass a comma-separated list, and a ping is delivered when it matches at least one value of every filter that is set. An organisation may hold 50 live-ping connections at once, counted across the raw and the processed stream together; the 51st is refused with 429.