Available Commands
- Charge — Start charging, stop charging, set charge limit
- Security — Lock and unlock vehicle doors
- Navigation — Set a destination in the vehicle’s navigation system
- Charge Port — Open and close the charge port door
- Charge Schedules — Configure daily, weekly, or workweek charging windows, or delete a schedule
VEHICLE_NOT_CAPABLE compatibility error:
ChargeTimers signal. Timers with "type": "LOCATION" include a scheduleType and scheduleId — use the scheduleId to issue DELETE requests. The signal reflects all schedules on the vehicle, including any set outside of the API.
Data State Changes
Commands do not return updated vehicle state. After issuing a command, confirm or monitor its effect by reading the corresponding signal — via the Vehicle Data API or webhooks. Signal updates may be delayed as the change propagates to the vehicle.Key Concepts
Always handle a 202
Any command or charge schedule request can return 202 Accepted, no matter how long you wait. Your integration must expect a 202 on every request and handle it as described below.
Smartcar works in the background to get each request through to the vehicle. How long that takes varies widely, even for the same command on the same vehicle. A request that finished in seconds yesterday can take minutes today, so a longer wait reduces how often you get a 202 but never rules it out.
A 202 is neither an error nor the final result. It’s a complete response: the body holds the execution with status.value set to PENDING, and the request keeps running after you receive it. To get the outcome, poll the execution URL until the status changes.
Setting the wait time
Each request waits up to 60 seconds by default before responding. SendPrefer: wait=<seconds> to change this, from 0 up to a maximum of 150 seconds:
- If the request finishes in time, you get the final result:
200with the execution, or an error status with an error response. - If it’s still running when the wait ends, you get a
202instead of a timeout.
wait, the 200 or 202 response includes a Preference-Applied header with the wait that was used, for example Preference-Applied: wait=150.
Getting the result after a 202
1
Read the 202 response
The
Location header holds the URL of the execution. It’s the same value as data.links.self in the body. The Retry-After header says how many seconds to wait before checking.2
Poll the execution
After
Retry-After seconds, send a GET to the Location URL with the same Authorization header. Commands use Get command execution; charge schedules use Get charge schedule execution.3
Repeat until it's no longer PENDING
Keep polling every
Retry-After seconds until status.value is SUCCESS, FAILURE, or EXPIRED.EXPIRED means the request reached Smartcar’s time limit before a result was recorded, so the outcome is unknown. You can check the outcome in signal data or retry the command.
To confirm that an execution belongs to your request, compare its
meta.requestId to the X-Amzn-Requestid header in the POST’s response. If they don’t match, the execution describes a newer operation.sc-user-id Header
All command endpoints require thesc-user-id header. Your bearer token is application-level and does not carry per-user context, so this header must be provided on every request to identify which user’s vehicle to act on.

