API Errors

The Upvest Investment API uses standard HTTP status codes and RFC9457 error types. The following table gives you an overview of all codes and error types.

Usually response codes in the range 2xx indicate a successful response, in the range 4xx a client error and in the range 5xx a server error (these are rare, however).

Code	RFC9457 Error Type	Description
400	Bad Request	The request contains some data which format does not conform to one that we expect. Check details value of the response to get additional information.
400	Missing Client ID	The `upvest-client-id` header is missing in the request.
400	Missing Idempotency Key	The request you are trying to execute requires `idempotency-key` in the header of the request.
401	Unauthorised	The call can not be authorised.
403	Forbidden	The request you are trying to execute requires certain authorisations associated with the access token you pass to the call.
404	Not Found	The server cannot find the requested resource.
406	Not Acceptable	The server cannot generate a response that matches the list of acceptable values defined in the request's proactive content negotiation headers, also the server is unwilling to provide a default representation.
409	Conflict	An operation is not available for the current status of the resource.
422	Unprocessable Entity	An entity could not be processed due to a semantic error.
429	Too Many Requests	You have sent too many requests in a given amount of time ("rate limiting").
500	Internal Server Error	The call has failed due to an internal problem. Our monitoring system has triggered an alert, and the issue is being investigated and resolved by our engineering team.
503	Service Unavailable	The server is not ready to handle the request.
504	Gateway Timeout	The server acted as a gateway or proxy and did not receive a timely response from the upstream server.

INFO

In the subchapters you will find the exact error descriptions and possible solutions for the Upvest-specific error types.