Fleet Connectivity Extension API Developer's Guide

HTTP Status Codes

Fleet Connectivity Extension API supports the standard HTTP status codes. When an request results in a 400 Bad Request response, the response body may contain addition troubleshooting information.

Status	Message	Error (description)	Example
400 Bad Request	Invalid Authentication	Change the parameters in the request to match your credentials. For more information on how to get user credentials, see Acquiring Credentials.	`{ "status" : "Bad Request", "message" : "Error occurred", "error" : "Invalid authentication." }`
400 Bad Request	Missing Parameters	Add the required parameters to the request. For more information on which parameters are required, see the appropriate reference for the resource (sendjob or listupdates).	`{ "status" : "Bad Request", "message" : "Missing parameters", "error" : "Required parameters \ have not been provided." }`
400 Bad Request	Unable to complete request	Check the diagnostic for additional information.
400 Bad Request	Unique key violation	The request contains a value for a parameter that duplicates information previously submitted to the system when that parameter must be unique. For example, the parameter `job_id` in a request to the resource `sendjob` contains an ID that was used in a previous request. Make a new request with a unique ID.	`{ "status" : "Bad Request", "message" : "There was a unique \ key violation. Check data \ input." , "error" : "Duplicate entry \ 'D133333-1' for key \ 'unique_customer_loc_id'" }`
Unauthorized	User not authorized for this action	"User does not have permission rights for export" or "User not authorized for this action".