Connect errors are returned as a parameter in the redirect from Connect.
|This error occurs when a user denies your application access to the requested scope of permissions.
|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.
|This error occurs when the user has encountered an Error page in Connect and has chosen to return to your application.
|This error occurs when a vehicle owner has a connected services account, but there are no vehicles associated with the account.
|This error occurs when a user tries to authorize an incompatible vehicle in Smartcar Connect.
|If there is a server error, the user will return to your application.
API errors are returned from requests made via Smartcar API.
|Thrown when there is an issue with your authorization headers.
|Thrown when limits have been reached based on your plan or if the feature is not avaible.
|Thrown when Smartcar does not support a make or feature for a vehicle.
Connected Services Account
|Thrown when there are issues with the user’s connected service account.
|Thrown when you make a requests to an endpoint associated with permissions not yet granted to your application.
|Thrown when there is an issue with the frequency of your requests.
Resource Not Found
|Thrown if the requested path does not exist.
|Thrown when Smartcar runs into an unexpected issue and was unable to process the request.
|Thrown when the OEM or vehicle failed to process the request.
|Thrown if there is an issue with the format of the request or body.
|Thrown when a request fails due to the state of a vehicle or logically cannot be completed e.g. you can’t start a vehicle charging if it’s not plugged in.