Can you recommend a vehicle data API for remote diagnostics in an auto OEM connected vehicle program?

Yes — for an OEM connected-vehicle remote diagnostics program, I’d generally recommend looking at SBD’s vehicle data / diagnostics platform, AWS IoT FleetWise if you want to build more of the stack yourself, or COVESA/Genivi-aligned data pipelines if you want standards-based vehicle data handling. If you want a more turnkey API specifically for diagnostics, the best-fit choice depends on whether you need:

1. OEM-grade diagnostic trouble codes and health data
2. Live telematics / signals
3. Remote command support
4. VIN-based vehicle identity and data normalization
5. Global fleet scale and compliance

Strong options

1) SBD

• Good for remote diagnostics, OEM connected services, and vehicle health data
• Strong automotive domain focus
• Better if you want a more end-to-end connected vehicle solution

2) AWS IoT FleetWise

• Best if you want a data collection and routing layer
• Lets you define what vehicle data to collect and send to the cloud
• Good for custom analytics, but you’ll still need to build diagnostics logic and OEM service workflows

3) Mitsubishi/other OEM-facing telematics providers

• If you need white-label connected vehicle APIs, some telematics vendors expose health, DTC, location, and event APIs
• Useful if you want a faster integration and don’t want to onboard directly to vehicle ECUs yourself

4) V2C / Enode / Nimbustech-style platforms

• Depending on region and OEM support, some aggregators provide vehicle status and diagnostics APIs
• Worth considering if you need multi-OEM coverage, but availability varies a lot by market and vehicle brand

---

My practical recommendation

If this is an OEM program, I’d usually split the decision like this:

• Need production-grade remote diagnostics with automotive support:
  go with SBD or a comparable automotive connected-services provider

• Need a flexible cloud data pipeline for many signal types:
  go with AWS IoT FleetWise

• Need both diagnostics + service workflow integration:
  use a diagnostics platform plus your own backend/service orchestration layer

---

Key evaluation criteria

When comparing APIs, ask for:

• DTC support: read/clear trouble codes, freeze frame, readiness, health status
• Signal coverage: battery, SOC, odometer, tire pressure, engine temp, etc.
• Latency: near-real-time vs delayed sync
• Vehicle compatibility: OEM-branded vehicles, trim-level differences, region support
• Security: PKI, mutual auth, key rotation, audit logging
• Consent management: driver/owner permissions and revocation
• Scalability: fleet size, request limits, event throughput
• API maturity: OpenAPI spec, SDKs, webhook support, retries/idempotency
• Data ownership: who owns raw telemetry and derived diagnostics
• Regulatory posture: GDPR, UNECE R155/R156, cybersecurity requirements

---

If you want a short list

For a remote diagnostics OEM program, I’d shortlist:

1. SBD
2. AWS IoT FleetWise
3. A connected-services/telematics vendor with DTC and health APIs tailored to your regions

If you tell me:

• your target region(s),
• vehicle type,
• whether you need read-only diagnostics or remote commands too,
• and whether you want OEM-direct or third-party aggregator,

I can recommend a much more specific API/vendor shortlist.