Overview
Nuonic uses data captured by telematics devices, combined with contextual data, to produce analysis of vehicle activity for reporting and operational workflows.
If you are a telematics provider, this integration allows your clients to use Nuonic as a value-added service leveraging their existing installed devices.
Data Transfer Methods
Nuonic can accept telematics data through one of the following methods.
1. REST API
If your telematics system provides a REST API with endpoints that expose the fields listed in our Telematics Data Input Specification, our team can work with you to build a Nuonic integration add-on that extracts data on a scheduled basis.
Nuonic supports production-grade extraction workflows including API rate limits and multi-client processing.
2. AWS S3 File Transfer
If your telematics system does not provide an API, you can send flat files in an agreed format aligned to Telematics Data Input Specification to an AWS S3 bucket provisioned for your integration.
This allows you to control when files are sent (daily is recommended). When files arrive, Nuonic processing can be triggered automatically by S3 events.
To use this option effectively, files should be supplied in a consistent format through automated processes. Manual exports/uploads are possible but are more error-prone.
3. Device Data Streams
If your devices or systems provide a real-time binary or encoded stream that can be directed externally, our team can provide an HTTP or WebSocket endpoint for Nuonic to capture the data.
This method can provide near real-time visibility, but it may not support historical backfill, which is commonly required by clients.
What to Share with Nuonic
When discussing a new integration, include:
- Provider platform name and product variant.
- Available transfer method (
REST API,S3 files, or stream endpoint). - Authentication model and API/file access details.
- Sample payloads or file extracts.
- Data refresh frequency and retention window.