Welcome to Quividi VidiCenter’s API documentation
Quividi’s customers can access their data on VidiCenter via a Web service:
Data is requested by accessing https://vidicenter.quividi.com/api/
Data is returned in the JSON format
Security is provided by token-based authentication
Access to VidiCenter’s REST API is an optional service that you must request explicitly to Quividi; only authorized customers will be able to generate the necessary authentication tokens.
Please be aware that any abuse of service (excessive number of requests per minute, repeated invalidation of the cache, etc.) will affect the quality of service experienced by all VidiCenter users; in this regard, Quividi reserves the right to disable access to the REST interface upon violation of the terms of service.
If we feel the volume of your requests may impact the performance of our service, the API may return responses with the 429 HTTP status code.
Additional information can be found in the related support article here
Contents:
- General usage
- Topology calls
- Networks list
- Sites list
- Sites list with vehicles factors
- Network’s sites list
- Network’s sites list with vehicles factors
- Site tag’s sites list
- Locations list
- Network’s locations list
- Site’s locations list
- Site tag’s locations list
- Location tag’s locations list
- Boxes list
- Network’s boxes list
- Site’s boxes list
- Site tag’s boxes list
- Location’s boxes list
- Location tag’s boxes list
- Status calls
- Alerts list
- Network’s alerts list
- Site’s alerts list
- Site tag’s alerts list
- Location’s alerts list
- Location tag’s alerts list
- Box’s alerts list
- Monitoring messages list
- Network’s monitoring messages list
- Site’s monitoring messages list
- Site tag’s monitoring messages list
- Location’s monitoring messages list
- Location tag’s monitoring messages list
- Box’s monitoring messages list
- Tags calls
- Data export
- Clip Metadata
- Charts
- OEM