Errors
Other errors
VALIDATION
Request invalid or malformed. Please check for missing parameters, spelling and casing mistakes, and other syntax issues.
{
"type": "VALIDATION",
"code": null,
"description": "Request invalid or malformed. Please check for missing parameters, spelling and casing mistakes, and other syntax issues.",
"docURL": "https://smartcar.com/docs/errors/v2.0/other-errors/#validation",
"statusCode": 400,
"requestId": "5dea93a1-3f79-4246-90c5-89610a20471b",
"resolution": { "type": null }
}
Suggested resolution
Troubleshooting steps
- Ensure that you spell and case all parameters correctly.
- Ensure that your request has the correct content-type (i.e.
application/json
orapplication/x-www-form-urlencoded
). - Ensure that your request has the correct URL and HTTP method.
Suggested user message
Your car is temporarily unable to connect to <app name>
. Please be patient while we’re working to resolve this issue.
AUTHENTICATION
The authorization header is missing or malformed, or it contains invalid or expired authentication credentials (e.g. access token, client ID, client secret). Please check for missing parameters, spelling and casing mistakes, and other syntax issues.
{
"type": "AUTHENTICATION",
"code": null,
"description": "The authorization header is missing or malformed, or it contains invalid or expired authentication credentials. Please check for missing parameters, spelling and casing mistakes, and other syntax issues.",
"docURL": "https://smartcar.com/docs/errors/v2.0/other-errors/#authentication",
"statusCode": 401,
"requestId": "5dea93a1-3f79-4246-90c5-89610a20471b",
"resolution": { "type": null }
}
Suggested resolution
Troubleshooting steps
- Refer to our API reference and ensure that you use the correct authentication mechanism for your request.
- Check constants like
Bearer
andBasic
for spelling mistakes. - If you make a request to a vehicle endpoint, verify that your access token grants you access to the correct vehicle. You can do so by making a request to the
/vehicles
endpoint and ensuring that the correct vehicle ID is included in the returned response. - If you have refreshed your access token, make sure that it persists and that you use your new token to make your request.
Suggested user message
Your car is temporarily unable to connect to <app name>
. Please be patient while we’re working to resolve this issue.
PERMISSION
Your application has insufficient permissions to access the requested resource. Please prompt the user to re-authenticate using Smartcar Connect.
{
"type": "PERMISSION",
"code": null,
"description": "Your application has insufficient permissions to access the requested resource. Please prompt the user to re-authenticate using Smartcar Connect.",
"docURL": "https://smartcar.com/docs/errors/v2.0/other-errors/#permission",
"statusCode": 403,
"requestId": "5dea93a1-3f79-4246-90c5-89610a20471b",
"resolution": { "type": "REAUTHENTICATE" }
}
Suggested resolution
You can resolve this error by ensuring that the scope parameter contains all the permissions that your application requires and prompting the user to re-authenticate using Smartcar Connect.
Troubleshooting steps
- Ensure that the scope parameter contains all the permissions that your application requires.
- Ensure that you spell all permission names in the
scope
parameter correctly. - Prompt the user to re-authenticate using Smartcar Connect.
Suggested user message
<App name>
does not yet have permission to <action>
your car. Please use this link to re-connect your car to <app name>
: <link to Smartcar Connect>
.
Examples for <action>
:
- Read the engine oil life of
- Read the EV battery capacity of
- Read the EV battery level of
- Read the EV charging status of
- Start charging
- Stop charging
- Read the fuel tank level of
- Locate
- Lock
- Unlock
- Read the odometer of
- Read the tire pressure from
- Read the make, model, and year of
- Read the VIN of
INTERNAL
An internal Smartcar error has occurred. Our team has been notified and is working to resolve this issue.
{
"type": "SERVER",
"code": "INTERNAL",
"description": "An internal Smartcar error has occurred. Our team has been notified and is working to resolve this issue.",
"docURL": "https://smartcar.com/docs/errors/v2.0/other-errors/#internal",
"statusCode": 500,
"requestId": "5dea93a1-3f79-4246-90c5-89610a20471b",
"resolution": { "type": "RETRY_LATER" }
}
Suggested resolution
Suggested user message
Your car is temporarily unable to connect to <app name>
. Please be patient while we’re working to resolve this issue.
PATH
The requested resource does not exist. Please check the URL and try again.
{
"type": "RESOURCE_NOT_FOUND",
"code": "PATH",
"description": "The requested resource does not exist. Please check the URL and try again.",
"docURL": "https://smartcar.com/docs/errors/v2.0/other-errors/#path",
"statusCode": 404,
"requestId": "5dea93a1-3f79-4246-90c5-89610a20471b",
"resolution": { "type": null }
}
Suggested resolution
You can resolve this error by referring to our API reference and ensuring that you use the correct URL for your request.
Troubleshooting steps
- Ensure that you spell all static parts of the URL correctly.
- Ensure that you use the correct URL path parameters (e.g. vehicle ID).
- Ensure that you use the correct HTTP method.
Suggested user message
Your car is temporarily unable to connect to <app name>
. Please be patient while we’re working to resolve this issue.
VERSION
The requested resource does not exist. Your request either does not specify a version number or it specifies a version number that is not supported by this resource.
{
"type": "RESOURCE_NOT_FOUND",
"code": "VERSION",
"description": "The requested resource does not exist. Please check your specified version number and try again.",
"docURL": "https://smartcar.com/docs/errors/v2.0/other-errors/#version",
"statusCode": 404,
"requestId": "5dea93a1-3f79-4246-90c5-89610a20471b",
"resolution": { "type": null }
}
Suggested resolution
https://api.smartcar.com/v2.0/vehicles
). Version 1 has been sunset and is no longer supported.Suggested user message
Your car is temporarily unable to connect to <app name>
. Please be patient while we’re working to resolve this issue.