Skip to main content
Subscribe to changelog updates and receive email notifications for new releases and updates.
​
March 11th, 2026

​
Vehicle Simulator now supports Smartcar Connect simulation

You can now test simulated vehicle connection flows in the Vehicle Simulator, including experiences that mirror how vehicle owners connect through Smartcar Connect.What’s new:
  • Connection-state testing — Create simulated vehicles in a disconnected state, then connect them later to test connection and reconnection behavior.
  • Two connection options — Connect simulated vehicles automatically, or run a full Smartcar Connect simulation flow with simulated credentials.
  • Brand simulation in Connect flow — Vehicles connected through simulated Connect reflect the selected brand in Dashboard views, webhook payloads, and API responses (vehicle.make).
  • Permissions parity for simulation — Simulator connection flows use the configured VehicleUserAccount.Permissions signal, which overrides app-level permissions.
  • Disconnect and resubscribe workflows — Disconnect simulated vehicles from Dashboard tables or via API, while preserving the simulated vehicle for future reconnection tests.
Get started: Create a simulated vehicle in the Dashboard to test automatic connection, Connect simulation, and disconnection scenarios in Vehicle Simulator.
​
March 10th, 2026

​
Powertrain Type Now Available in Webhook and API V3 Responses

The vehicle object in VEHICLE_STATE webhook payloads and API V3 responses now includes a powertrainType field. This field indicates the vehicle’s powertrain and returns one of the following values: BEV (Battery Electric Vehicle), PHEV (Plug-in Hybrid Electric Vehicle), ICE (Internal Combustion Engine), or HEV (Hybrid Electric Vehicle).Example webhook payload:
{
  "vehicle": {
    "id": "9af13248-3b73-4c9d-9a4b-d937ce6bc8e2",
    "make": "TESLA",
    "model": "Model 3",
    "year": 2020,
    "powertrainType": "BEV"
  }
}
Developers can use this value to filter data and tailor different customer experiences based on powertrain type. For example, you can show battery level for BEV vehicles, fuel level for ICE vehicles, or both for PHEV vehicles.Get started: The powertrainType field is automatically included in all VEHICLE_STATE webhook deliveries and API V3 vehicle responses — no configuration changes are needed. See the VEHICLE_STATE webhook reference for the full payload structure.
​
February 18th, 2026

​
Tesla Virtual Key Pairing flow improvements

We’ve improved the Tesla Virtual Key Pairing experience to make recovery from first-attempt failures clearer and faster.
Tesla virtual key relaunch prompt screenTesla virtual key warning and retry screen
What’s new:
  • Clearer retry guidance — If the “Add virtual key” prompt does not appear in the Tesla app, users are now prompted to try again since the second attempt often succeeds.
  • New “Relaunch Tesla” action — Vehicle owners can immediately relaunch the Tesla app from the pairing flow and retry without returning to the vehicle list.
​
February 17th, 2026

​
All-New Vehicle Simulator

Smartcar Vehicle Simulator V2
We’ve rebuilt the Vehicle Simulator from the ground up. The new simulator gives you full control over your simulated vehicle’s state and lets you test your Smartcar integration end-to-end — including webhooks — without needing a real vehicle.What’s new:
  • Configuration-based testing — Directly configure your simulated vehicle’s state and see changes reflected immediately in API responses and webhook deliveries. No more waiting for trips to play out.
  • Webhook testing — Subscribe simulated vehicles to your existing webhook integrations and trigger deliveries by publishing vehicle state changes. Test your full webhook pipeline without a live vehicle.
  • Full signal configuration — Configure all available signals organized by signal group, with default values provided for every signal. The signal groups match the same structure you see when setting up vehicle permissions for your application.
  • Permission simulation — Toggle individual permissions on or off to test how your application handles partial permission grants and permission errors.
  • Vehicle commands — Test lock/unlock, start/stop charge, set charge limit, and send destination. Commands trigger realistic state changes on the simulated vehicle.
  • Error state testing — Recreate error scenarios like permission denials or in-motion lock attempts to validate your application’s error handling.
The previous simulator remains available as Vehicle Simulator (Legacy).Get started: Open the Simulator in your Smartcar Dashboard and create your first simulated vehicle.
​
January 28th, 2026

​
Charging signal CONNECTOR replaced with CHARGING_TYPE is now live

The charging signal change announced on January 12th is now live. The CONNECTOR type has been replaced with CHARGING_TYPE in the following signals:
  • Charge.ChargeLimits
  • Charge.ChargeRecords
  • Charge.ChargeTimers
These signals now return the charging current type (AC or DC) instead of a connector hardware type. If your integration parses any of these signals and still references the CONNECTOR type, update your code to use CHARGING_TYPE and parse the chargingType field.For full details on the change, see the original announcement below.
​
January 20th, 2026

​
Send Destination now available for Volkswagen

You can now use the Smartcar API to send destinations to Volkswagen vehicles in the United States.With the Send Destination command, your application can route a destination directly to a driver’s built-in navigation screen. This unlocks new workflows:
  • Fleet management: Route drivers to their next pickup, delivery, or service location
  • Car sharing and rentals: Send return location addresses when a rental period is ending
  • Repair and maintenance: Direct customers to your nearest service center when maintenance is needed
  • Charging networks: Guide EV drivers to available chargers when battery is low
Get started: Request the control_navigation permission during the Smartcar Connect flow and call Send Destination.
​
January 16th, 2026

​
Ruby SDK and Java SDK Updated to Support Version 3 of the Vehicles API

The Ruby SDK and Java SDK have been updated to support Version 3 of the Vehicles API.Both SDKs now include three new methods:
  • get_vehicle - Retrieve vehicle information
  • get_signal - Get a specific signal for a vehicle
  • get_signals - Get all available signals for a vehicle
These new methods provide easier access to vehicle data through the latest API version, enabling developers to work with Smartcar’s expanded signal catalog and improved data delivery capabilities.Get started: Update to the latest SDK version and explore the new methods in the Ruby SDK and Java SDK documentation.
​
January 14th, 2026

​
Volvo Cars Partner Integration now available!

Smartcar is excited to announce a partnership with Volvo Cars, providing access to vehicles across the United States and Europe.What’s new:
  • Access charging, battery, location, and odometer data through Smartcar signals
  • Use the updated consent flow through Volvo’s official portal
Learn more in the Volvo integration updates.
​
January 12th, 2026

​
Upcoming change: Charging signal CONNECTOR to CHARGING_TYPE

On January 28th, 2026, we’re updating three charging-related signals. This is a breaking change that may require updates to your integration.Affected signals:
  • Charge.ChargeLimits
  • Charge.ChargeRecords
  • Charge.ChargeTimers
What’s changing: In all three signals, the CONNECTOR type is being replaced with CHARGING_TYPE. Instead of returning a connector hardware type (e.g., J1772), these signals will now return the charging current type (AC or DC).Before (current format):
{
  "type": "CONNECTOR",
  "condition": {
    "connectorType": "J1772"
  }
}
After (new format):
{
  "type": "CHARGING_TYPE",
  "condition": {
    "chargingType": "AC"
  }
}
Other types such as GLOBAL and LOCATION remain unchanged.Why we’re making this change: OEMs report connector hardware types inconsistently—some return proprietary strings, others return nothing at all. In contrast, AC vs. DC charging type is more widely provided across manufacturers.This change gives you more consistent, actionable data. Rather than maintaining a mapping of connector type strings, you can rely on a simple AC or DC value to determine whether the vehicle is on Level 1/2 charging or DC fast charging.What you need to do: If your integration parses any of these signals and handles the CONNECTOR type, update your code to:
  • Expect CHARGING_TYPE instead of CONNECTOR
  • Parse chargingType (values: AC or DC) instead of connectorType
Timeline:
  • Now -> January 27th, 2026: Current format remains in place
  • January 28th, 2026: New format goes live
Questions? Reach out to your Smartcar account manager or contact support.