Pareto APIs
Consume data from Pareto via REST API or WebSocket
Pareto features two types of APIs which address the typical application data needs of either push or pull?
The WebSocket API pushes every event from Pareto to the client in real-time. This is suited to applications which:
- respond or take action in real-time
- are highly sensitive to latency
- require a complete view of current system state
The REST API allows the client to query the current state on demand. This is suited to applications which:
- respond or take action periodically or in near-real-time
- are user-driven
- require only a specific view of current system state
Follow the links below for documentation specific to the RTLS and Contextual APIs.
Browse APIs
WebSocket for real-time events and REST for periodic queries
Websocket: Consume Pareto's real-time stream of contextual events either server-side or client-side.
Read documentation
RTLS: Query real-time location and sensor data via REST.
Read documentation
Contextual: Query real-time location and associated contextual metadata via REST.
Read documentation