Error Codes

Error Codes | FleetUp API Docs

When using the FleetUp API, you may encounter various errors. The following table lists common error codes, their causes, and solutions:

CODE	DESCRIPTION
204 - No Content	Cause: The request was successful, but there is no content to return. Solution: This is a normal response when there is no data to return. No action is required.
400 - Invalid Request	Cause: The request body format is invalid. Solution: Modify the request body according to the hints in the error message. For more details on API formats, refer to the FleetUp API Documentation.
401 - Unauthorized	Cause: Authentication failed due to an incorrect API key or token. Solution: Check your API key or token. If you do not have one, create an API key in your FleetUp Account Settings.
403 - Forbidden	Cause: You do not have permission to access the requested resource. Solution: Ensure that you have the necessary permissions or contact FleetUp support for assistance.
404 - Not Found	Cause: The requested resource could not be found. Solution: Verify the endpoint URL and resource ID. If the issue persists, contact FleetUp support.
405 - Method Not Allowed	Cause: The HTTP method used is not allowed for the endpoint. Solution: Use the correct HTTP method (e.g., GET, POST) for the endpoint as specified in the API documentation.
422 - Unprocessable Entity	Cause: The request contains invalid parameters. Solution: Modify the request parameters according to the hints in the error message. For more details on API formats, refer to the FleetUp API Documentation.
429 - Too Many Requests	Cause: You are sending requests too quickly. Solution: Adhere to the API rate limits. FleetUp APIs can be called once per second, but we recommend a 10-second interval for significant data changes.
500 - Internal Server Error	Cause: The server encountered an unexpected error. Solution: Retry the request after a brief wait. If the issue persists, contact FleetUp support.
503 - Service Unavailable	Cause: The server is temporarily unable to handle the request due to maintenance or overload. Solution: Retry the request later. Check FleetUp’s service status page or contact support for updates.

Example Error Responses

204 - No Content

{
  "message": "No content to return."
}

400 - Invalid Request

{
  "error": {
    "code": 400,
    "message": "Invalid request body: missing required field 'acctId'.",
    "details": "Ensure that the 'acctId' field is present and valid in the request body."
  }
}

401 - Unauthorized

{
  "error": {
    "code": 401,
    "message": "Authentication failed: Invalid API key provided.",
    "details": "Please use a valid API key or token in the 'Authorization' header."
  }
}

429 - Too Many Requests

{
  "error": {
    "code": 429,
    "message": "Rate limit exceeded: You have exceeded the maximum allowed requests per second.",
    "details": "Please wait for a few seconds before making additional requests."
  }
}

Key Notes

Error Codes: Use the HTTP status code for the CODE (e.g., 400, 401, 500).

Error Handling: Always include a details field in error responses to provide additional context for troubleshooting.

Support: For persistent issues or unexpected errors, contact FleetUp support for assistance.

Error Codes | FleetUp API Docs#

Example Error Responses#

204 - No Content#

400 - Invalid Request#

401 - Unauthorized#

429 - Too Many Requests#