RTLS API
Query real-time location and sensor data via REST
The RTLS API is suited for occasional or periodic location and/or sensor queries based strictly on device identifiers. The RTLS API answers: what is the current location and packet payload?
Pareto's RTLS API queries are identical to those of reelyActive's barterer open source software (OSS) package. Applications built on the RTLS API will be compatible with both Pareto and the OSS. Packet payloads are decoded using reelyActive's advlib OSS package.
Both JSON and HTML are supported: any route can be queried via browser for a human-readable response.
The /whereis route provides real-time location data and the most recent packet payload. The query is performed on a specific transmitter based on:
- a transmitter identifier, for example:
pareto.reelyactive.com/whereis/transmitter/fee150bada55
Consult the barterer documentation for details concerning:
The /whatat route provides real-time location data and the most recent packet payloads. The query is performed on a specific receiver based on:
- a receiver identifier, for example:
pareto.reelyactive.com/whatat/receiver/001bc50940810000
Consult the barterer documentation for details concerning:
The /whatnear route provides real-time location data and the most recent packet payloads. The query is performed on a specific transmitter based on:
- a transmitter identifier, for example:
pareto.reelyactive.com/whatnear/transmitter/fee150bada55
Consult the barterer documentation for details concerning:
Additional API Documentation
WebSocket for real-time, or take another REST for periodic queries
Websocket: Consume Pareto's real-time stream of contextual events either server-side or client-side.
Read documentation
Contextual: Query real-time location and associated contextual metadata via REST.
Read documentation