This page applies to Connect flows that end in a redirect. If you launch Connect with
response_type=none and no redirect_uri, there is no response to handle: the flow ends on a Smartcar-hosted completion page, and you can look up the new connection on the /connections endpoint.Success
A Smartcar-generated UUID that identifies this user. Store this ID alongside your internal user identifier — you will use it as the
sc-user-id header when making API requests on behalf of this user.The
external_id you passed in the Connect URL, echoed back so you can match this connection to your records. Only present if you set one.If the redirect to Smartcar Connect contains a state parameter, that parameter will be returned here.
Success
Error
For a detailed description of these errors, please see our errors page.If the redirect to Smartcar Connect contains a state parameter, that parameter will be returned here.
Error
In addition to the error code and description, Smartcar will return the following parameters when a
user tries to authorize an incompatible vehicle in Connect.
What’s Next
Now that you have auser_id, here’s what you can do with it:
- API Authentication — Get an application access token to make API requests
- API Overview — See what data and commands you can access
- Vehicle Data — Read signals like battery level, odometer, and location
- Vehicle Commands — Lock, unlock, start/stop charging, set destination, and more
- Connections — List and manage this user’s vehicle connections
user_id as the sc-user-id header on any request to scope it to this user.
