Smartcar
Connect Smartcar to the rest of your business, with the right person approving what changes and a record of every action.
16 ways to read.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Smartcar, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- List granted permissions
permissions.listRead
Example flow
- Smartcar · List granted permissions
permissions.listDone - Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Smartcar.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Smartcar
- Smartcar's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Smartcar test account before you go live.
For developers
Technical detail
Read consenting owners' vehicles through Smartcar: attributes, VIN, odometer, location, EV battery and charge state, fuel, tyres, oil and lock status.
Smartcar API docs- Source actions
- 16
- Data types
- 16
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
battery capacity1
- Get EV battery capacitySource
Read the nominal battery capacity in kWh.
battery1
- Get EV battery levelSource
Read state of charge and electric range (BEV and PHEV only).
charge limit1
- Get charge limitSource
Read the configured charge limit. Setting the limit is excluded.
charge1
- Get charge statusSource
Read whether the EV is plugged in and charging. Does not start or stop charging.
engine oil1
- Get engine oil lifeSource
Read remaining engine oil life.
fuel1
- Get fuel tankSource
Read fuel level, amount and range.
location1
- Get locationSource
Read the vehicle's last reported latitude and longitude.
lock status1
- Get lock statusSource
Read whether the vehicle is locked and which doors, windows and storage are open. Locking and unlocking are excluded.
odometer1
- Get odometerSource
Read the current odometer reading.
permissions1
- List granted permissionsSource
Read the permissions the owner granted for one vehicle.
tires1
- Get tyre pressureSource
Read the pressure of all four tyres.
user1
- Get vehicle owner IDSource
Read the Smartcar user ID of the owner who granted access.
vehicle batch1
- Batch read vehicle signalsSource
Read several signals for one vehicle in a single request. Only read paths are accepted.
vehicle1
- Get vehicle attributesSource
Read make, model and year.
vehicles1
- List authorised vehiclesSource
Read paginated vehicle IDs linked by the authorised user.
vin1
- Get VINSource
Read the manufacturer vehicle identification number.
Access and limits
- Authentication
- Smartcar Connect user access token (Bearer)
- Plans and access
- Smartcar application with the vehicle owner's consent through Smartcar Connect for the read permissions used. Each signal needs its own permission (read_vehicle_info, read_vin, read_odometer, read_location, read_battery, read_fuel, read_tires, read_engine_oil, read_charge, read_security). Availability depends on make, model, country and connected-services subscription.
- Test environment
- Smartcar simulated vehicles are available in test mode.
- Rate limits
- Smartcar limits requests per vehicle and per application; HTTP 429 RATE_LIMIT responses use bounded retries and Retry-After. Batch requests count each path.
- Pagination
- Vehicle and permission lists use offset and limit (maximum 50); paging.count provides the total.
- Provider events
- Smartcar webhooks deliver scheduled or event-based vehicle data. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Vehicle availability depends on country, manufacturer, model and connected-services subscription.
- Smartcar documents the Vehicles API v2.0 as deprecated on 1 December 2026 in favour of v3 (vehicle.api.smartcar.com, signals).
- Vehicle commands are intentionally excluded because they act in the physical world: lock, unlock, start or stop charge, set charge limit and send navigation destination. Disconnecting vehicles or deleting users is also excluded.
- Access tokens expire after two hours and are not refreshed automatically; replace the stored token or reconnect through Smartcar Connect.
- Location is personal data; use vehicle location only with the owner's consent and for the stated purpose.
- The GET /v2.0/user path follows Smartcar's SDKs; the user page notes it is served from a different path during the v3 transition and may be deprecated.
Developer reference
- Create the Smartcar credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Smartcar, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/smartcar and the Connections API.