HTTP response codes

The NFleet APIs respond with HTTP response codes that match the HTTP specification semantics as closely as possible. The common responses returned by the NFleet APIs are the following.

200 OK The request completed successfully.

303 See Other The request is in progress and the client should continue the request by performing GET to the address designated by the Location header of the response.

400 Bad Request The request data has an error. The errors are described in the response using error message and an error code. See the API-specific error codes details.

401 Unauthorized Authentication failed for the request. Make sure the authorization scheme Bearer is designated and that the access token is valid.

403 Forbidden Authorization failed for the request. The authenticated client does not have permission to perform the request. Make sure that the client has requested an access token for an identity with the necessary permissions.

404 Not Found The requested resource was not found. Make sure the request URL is correct. If Not Found is encountered during long-running operation, a timeout may have occurred between requests and the request should be sent again.

405 Method Not Allowed The HTTP method used is not allowed to the requested URL. Check the HTTP header Allow for list of allowed method to this resource.

406 Not Acceptable The HTTP header Accept contains value that the server cannot use as a response format. Check the documentation for supported Accept header values for the given operation.

415 Unsupported Media Type The HTTP header Content-Type is missing or contains value that the server does not support. Use the application/json content type for API requests.

429 Too Many Requests The client has sent too many requests in a given amount of time. Refer to your NFleet subscription details on the request quotas applicable for the client. Check the Retry-After response header for the number of seconds the client must wait before making a new request.

500 Internal Server Error The server encountered an unexpected error. The request should be sent again. If the issue persists, contact NFleet support at support@nfleet.fi.

503 Service Unavailable The server is currently not available. The request should be sent again after a delay. If the issue persists, contact NFleet support at support@nfleet.fi.