Skip to content

/problems/fleet-not-supported⚓︎

Problem

This is a description of a specific error response that you can receive when using the INVERS OneAPI via REST.1

Check out our API Basics to learn more about the basic structure of all error responses and to find out how you should handle them.

{
    "type": "/problems/fleet-not-supported",
    "type_documentation": "https://developers.invers.com/problems/fleet-not-supported",
    "title": "Request is not supported by the current fleet.",
    "status": 400,
    "detail": "…",
    "flow_id": "5e77e3e3-48ab-4955-8ab3-1c62339096ab"
}

Meaning⚓︎

This problem type occurs when a request is used but the fleet does not support that feature.

Details⚓︎

  • Use the error response’s type property to handle specific errors and exception handling within your application. It’s comparable to an error code.
  • The detail property contains additional, more human-readable information about the problem or error. This is explanatory text and you should not have any exception handling and error handling code depend on it, as it may change.

Detail examples⚓︎

The following examples are typical texts which you might receive in the error response’s detail property. Note that it is not a complete list of all possible cases. Therefore expect to receive error responses with a detail property value not listed below.

Unable to request a vehicle state while the rental status of the vehicle ‘JQ7RP’ is ‘IN_RENTAL’. The data protection package ‘Remote Service’ is required to do this.

You’re attempting to request a vehicle’s state while it’s rental status is IN_RENTAL. Without the data protection package ‘Remote Service’, the command is only available when the vehicles is NOT_IN_RENTAL.

Possible solutions:

  • Try the request again when the vehicle is no longer rented out.
  • Contact the INVERS support if you are getting this error and your fleet should have the data protection package ‘Remote Service’.
The ‘tracking’ feature is not activated for the vehicle’s fleet.

You’re attempting to configure or use a feature that is not active for your fleet.

Possible solutions:

  • Contact INVERS support if you believe there is an error, please reach out to our support team for further assistance.

Further reading⚓︎


  1. The flow_id is specific to each API call, so it will be different in your case. However, type, title and status will match your actual error response if you receive the error described on this page.