Connect every vehicle to your own software
FlexConnect links every FlexCase to the cloud and gives OEMs and fleet operators an API to read live and historical data, send commands, and deliver updates. Use it to build the tools your customers need, or start with our ready-made dashboard.
import requests r = requests.get( "https://api.audesseinc.com/api/telemetry/FLX-0042/last", headers={"Authorization": f"Bearer {TOKEN}"}, params={"field": "BatteryVoltage"}, ) print(r.json()["readings"][0]["value"])
# Latest battery voltage from one FlexCase curl -G https://api.audesseinc.com/api/telemetry/FLX-0042/last \ -H "Authorization: Bearer $FLEXCONNECT_TOKEN" \ --data-urlencode "field=BatteryVoltage"
const res = await fetch( "https://api.audesseinc.com/api/telemetry/FLX-0042/last?field=BatteryVoltage", { headers: { Authorization: `Bearer ${TOKEN}` } } ); const { readings } = await res.json();
{
"device_id": "FLX-0042",
"readings": [{
"field": "BatteryVoltage",
"value": 26.8,
"timestamp": "2026-10-07T16:42:05Z"
}]
}Designed as one system
Audesse develops the controller, the connection, and the cloud services together, so they work as one. Data comes in from the vehicle, your software decides what to do, and changes go back to the same vehicle, with fewer integration gaps to manage.
ReadThe FlexCase logs the signals you choose, at rates you configure per message.
DecideYour software applies your business rules.
ActSend a command, a configuration change, or an update back to the vehicle. Commands are supervisory requests, and the FlexCase keeps final authority.
What the API can do
Every FlexConnect capability is available through the API, giving your software complete control.
Give each customer the access they need
OEMs get an administration panel for creating API access tokens. Each token can be limited to specific permissions and specific vehicles, so you can support several customers on FlexConnect and give each one its own experience.
Example tokens. Select one to see which vehicles it can reach.
Customer A fleet
Customer B fleet
Test vehicles
Develop and test faster
Integrators building control software on FlexCase use FlexConnect as part of their development loop, not only after the vehicle is deployed.
- See inside your algorithm: Log internal variables from your control application, like commanded and actual torque or controller states, and compare them over any test run.
- Shorter test loops: Push a new build over the air, run the test, and pull the results through the API, without visiting the vehicle.
- Compare software versions: Query the same signals before and after a change to confirm it did what you intended.
- Debug your clients' vehicles remotely: Fault-triggered capture records high-rate data around each fault, so you can diagnose without a site visit.
- Share data with your client: Give your client's engineers a read-only token limited to their vehicles.
- Reuse the same setup on every project: No new logging pipeline for each client, and each project stays separate through its own tokens.
Illustrative example
Use FlexConnect with your AI assistant
Audesse provides an MCP server for FlexConnect. MCP (Model Context Protocol) is an open standard that lets AI assistants connect to outside tools. With it, an assistant can work with your FlexConnect data through the API.
Ask questions of your fleet data
Ask in plain language and the assistant pulls the data it needs from the FlexConnect API, then summarizes, charts, or writes it up.
- Compare idle time across vehicles for the last month
- Summarize charging sessions by depot
- Draft a weekly maintenance report from fault codes and engine hours
Build your own tools faster
Use an AI coding assistant with the MCP server to write software that calls the FlexConnect API: desktop apps, mobile apps, scripts, and integrations with your other systems.
While you buildThe assistant connects with the same access tokens as any other application, so you can limit it to read-only access and to specific vehicles as needed.
Run your own applications on the vehicle
A FlexCase can be equipped with an onboard application processor alongside its automotive microcontroller, and your applications can run on both. FlexConnect deploys, updates, and communicates with them.
Microcontroller
Your real-time application- Your control application logic, running in real time
- I/O and vehicle network access
- Control and safety functions, designed to support up to ASIL D
Application processor
Your edge application- Machine learning, vision, and sensor fusion
- Process and reduce data before it is uploaded
- Custom logic, protocols, and integrations
Select a feature to see its details.
Core API capabilities
Fleet Overview
One request returns the key signals for every vehicle you can access, ready for a map, a status board, or a morning report.
What you can do with it- Show every vehicle's location and status on a map
- Spot faults and offline vehicles at a glance
- Limit the overview to the signals you care about
| Vehicle | Status | Battery | Last update |
|---|---|---|---|
| A-1 | Online | 78% | 2 s ago |
| A-2 | Online | 64% | 5 s ago |
| B-2 | Hub temperature high | 26.1 V | 1 s ago |
| T-1 | Offline | No data | 3 h ago |
Illustrative example
Time-Series History
Ask for any logged signal over any time range. FlexConnect splits it into windows and returns the mean, maximum, or other aggregate for each, so a long time range comes back as a chart-ready series.
What you can do with it- Compare vehicles over the same period
- Feed trends into maintenance planning
- Pull several signals in one request
Illustrative example
Data Export
Pull raw or aggregated history for each vehicle and write it wherever you need it. Because export runs through the API, the format is up to you.
What you can do with it- Choose the aggregation that fits your analysis
- CSV files for engineering analysis
- Your own retention and archiving rules
timestamp,vehicle,signal,value 2026-10-07T16:40:00Z,A-1,BatteryVoltage,26.8 2026-10-07T16:40:00Z,A-1,CoolantTemp,82.4 2026-10-07T16:40:00Z,A-2,BatteryVoltage,26.5 2026-10-07T16:40:00Z,A-2,CoolantTemp,79.9
Illustrative example
Latest Values
Get the most recent reading of any signal, for one vehicle or many, to drive your own apps and integrations.
What you can do with it- Show live values in your own app
- Check a vehicle's state before sending a command
- Trigger actions in your own software
Illustrative example
Remote Commands
Send CAN messages and change FlexCase configuration from your own software, for any vehicle.
What you can do with it- Set a charging limit or a geofenced speed limit
- Change logging behaviour without a site visit
- Label vehicles and add notes for your team
| Time | Vehicles | Command | Status |
|---|---|---|---|
| 10:41 | B-2 | Send CAN message: limit power | Applied |
| 10:38 | A-3 | Change sample rate | Applied |
| 10:35 | A-5 | Update charging schedule | Applied |
| 10:30 | T-1 | Update configuration | Pending |
{ "type": "modify_sample_time",
"device_id": "FLX-0042",
"sample_time": 0.01 }Illustrative example
Over-the-Air Updates
Ship new versions of your FlexCase application software to vehicles in the field.
What you can do with it- Fix issues without a service visit
- Deliver new features to vehicles already on the road
- Update supported third-party ECUs
Illustrative example
Remote Decoding
Upload your DBC files once, and signals arrive decoded, named, and in engineering units. When your vehicle changes, update the DBC without touching the vehicle.
What you can do with it- Use your own proprietary messages
- Work with standard J1939 and OBD-II signals
- Query signals by name instead of raw CAN IDs
0x18FEF100 F3 2F 1E FF FF FF FF FF 0x0CF00400 F0 7D 7D 40 1F FF FF FF
| Signal | Value |
|---|---|
| WheelBasedVehicleSpeed | 30.2 km/h |
| EngineSpeed | 1,000 rpm |
Illustrative example
Configurable Logging
Set the logging rate for each message, change upload intervals, and capture high-rate data around specific events.
What you can do with it- Log fast signals quickly and slow signals slowly to control data costs
- Capture three minutes before and after each DTC
- Change settings per vehicle
| Message | Logging rate |
|---|---|
| Engine speed | 10 ms |
| Wheel speeds | 10 ms |
| Battery voltage | 1 s |
| GPS position | 1 s |
| Cabin temperature | 10 s |
Illustrative example
FlexCase Identity
Every FlexCase is provisioned with its own certificate, so FlexConnect knows exactly which vehicle each connection comes from.
What you can do with it- Attribute every reading to the right vehicle
- Identify and manage each FlexCase individually
- Combine with access tokens to control who sees what
Together, the FlexCase certificate and the access token decide which data reaches whom.
Illustrative example
Select a capability to see an example.
- Documented with OpenAPI 3.1, so you can generate a client in your language
- Batch endpoints for fleet-scale queries
What you can build
With the API, FlexConnect can become part of your own product rather than a separate tool. A few examples by vehicle type:
Depot charging orchestration
Read state of charge and departure times. Act by throttling chargers to stay under the site limit.
Electric vehicles → HydrogenShared refuelling windows
Read hydrogen level and stack hours. Act by scheduling the dispenser and setting the power split.
Hydrogen vehicles → TowedHot wheel-end detection
Read hub temperatures and ABS faults. Act by flagging the trailer and holding it from dispatch.
Towed vehicles → AutonomousGeofenced operating limits
Read location and system health. Act by lowering limits inside yards, ports, and job sites.
Autonomous vehicles → ConventionalAnti-idling & parked regeneration
Read idle time and DPF status. Act by shutting down where bylaws apply and regenerating at the depot.
Conventional vehicles →Features specific to your product
Warranty analytics, usage-based service plans, or paid features enabled over the air.
Discuss your application →
Airport Technologies Inc.: remote support for airport snow removal fleets
ATI builds snowplows, de-icers, and runway sweepers that operate at airports across a wide area, often with no service staff on site. With FlexCase and FlexConnect, ATI updates software on controllers and displays from multiple suppliers remotely, reads and clears diagnostic trouble codes without a site visit, and uses operating data to plan maintenance.
Read the case study →Use the API, the dashboard, or both
Both use the same platform and the same data.
Use the API
Connect FlexConnect to your own software and present it under your own brand.
- Your UI, your workflows, your business logic
- Connect any system that can call a REST API
- Script commands, configuration, and updates
- Export your data in any format you choose
Use the dashboard
A ready-made Grafana dashboard with no code required.
- Live data, history, and maps
- White-label it with your branding
- Viewer and editor accounts for your team
Many teams start with the dashboard and add API integrations as their needs grow.
How FlexConnect compares
Standard telemetry systems are built to move data off a vehicle. FlexConnect is built around the vehicle controller, by a team that develops automotive control systems.
You can build it yourself. FlexConnect provides the same architecture, already integrated with the controller and maintained by Audesse, so your engineers can focus on your vehicle.
| Generic telematics unit | FlexConnect | Build it yourself | |
|---|---|---|---|
| Data available | What is broadcast on CAN | High-rate internal controller signals | Whatever you build |
| Sending commands | Often limited or unauthenticated | Can be authenticated from the cloud to the controller | You design and secure the whole path |
| Vehicle networks | Often OBD-II or a fixed list of signals | CAN, J1939, OBD-II, and Ethernet, with CAN decoded using your own DBC files | You build it |
| Remote diagnostics | Fault codes, where the vehicle reports them | UDS diagnostics on any UDS-capable controller on the vehicle network | You build it |
| Over-the-air updates | Rarely included | Controller and edge application software, plus supported third-party ECUs | You build and maintain it |
| Edge computing | Limited or none | Optional onboard application processor, managed through FlexConnect | Separate hardware to integrate |
| Your own UI and integrations | Limited to the vendor's screens | Full REST API, plus an optional dashboard | Yes, after you build everything else |
| Hosting | The vendor's shared cloud | Shared, or an isolated instance in your region for Enterprise customers | Your own servers |
| Infrastructure to maintain | None | None | All of it |
Common questions
We already have telematics. Do we have to replace it?
No. FlexConnect is additive. Most customers start with a pilot on part of the fleet and expand from there.
What happens when a vehicle loses its connection?
Policies are enforced on the FlexCase itself, so they keep working offline. Data is logged on the FlexCase and forwarded when the connection returns.
Isn't remote control a new attack surface?
Commands are supervisory requests, not direct control of actuators. They can be authenticated from the cloud to the controller, each FlexCase has its own certificate, and the controller on the vehicle keeps final authority.
Who owns the data?
You do. Pull it through the API at any time and export it in whatever format you need, whether that is CSV files, your own database, or a data lake.
Where is FlexConnect hosted?
Enterprise customers can have FlexConnect run as an isolated instance on servers in their region of choice, for added reliability and uptime.
Are we locked in?
FlexConnect uses standard vehicle interfaces and a documented REST API in the cloud. Your data stays exportable.
Do I need to write code to use FlexConnect?
No. The Grafana dashboard works out of the box. The API is there when you want to go further.
How is FlexConnect priced?
Industrial plans are pay-as-you-go for smaller fleets. Enterprise plans offer predictable per-vehicle pricing for larger fleets. See the pricing page for details and a cost calculator.
Does FlexConnect work with hardware other than FlexCase?
Yes. FlexConnect is supported on all FlexCase models, and the FlexConnect API also supports other telematics hardware. Other hardware may not offer all of the features available on a FlexCase.
Get started
Contact us about API access, a dashboard demo, or a pilot on part of your fleet.