Test errors

Test error statuses

You can use test mode to verify that your application properly handles various error statuses that Smartcar may return. There are two types of errors that can occur after integrating Smartcar into an application:

1. Connect errors
2. Request errors

1. Connect errors

access_denied

This error occurs when a user denies your application access to the requested scope of permissions. To test this error, launch Smartcar Connect in test mode and select “Deny access” on the permissions screen.

We recommend handling this error by re-prompting the user to authorize their vehicle and adding a message like in the example below.

vehicle_incompatible

This error occurs when a user tries to authorize an incompatible vehicle in Smartcar Connect. In order to be compatible, a vehicle must:

1. Have the hardware required for internet connectivity
2. Belong to the makes and models Smartcar is compatible with
3. Be capable of the required permissions that your application is requesting access to

If the user’s vehicle is incompatible, Smartcar will let the user know and offer them to share their vehicle’s VIN, make, model, and year with your application.

We recommend that your application provides a flow for incompatible vehicles like in the example below.

invalid_subscription

This error occurs when a user’s vehicle is compatible but their connected services subscription is inactive because either it has expired or it has never been activated. Smartcar will direct the user to the connected services website to (re-)activate their subscription. However, a user may choose to return back to your application instead, like in the example below.

2. Request errors

The following request errors can be tested using Smartcar’s test mode.

1. vehicle_owner_action_required: This error occurs when a user has either changed the password of their connected services subscription or their subscription has expired. You should prompt your user to take the necessary action.
2. vehicle_state_error: This error occurs when a vehicle is unable to perform the request in its current state. For example, the vehicle might be outside of a cellular coverage area or the vehicle’s doors might stand open while a lock request is initiated. See the error codes below for a detailed list of all possible scenarios. Depending on the scenario, you should try sending another request at a later time or prompt your user to take the necessary action.

To test these errors, launch Smartcar Connect in test mode and log in with one of the following emails and any password. Then make a request to any non-static vehicle endpoints (all endpoints under the /vehicles resource, excluding the VIN, vehicle attributes, and application permissions endpoints).