Successful response

Bad requests generally mean the client has passed invalid
or malformed parameters. Error messages in the response could help in
evaluating the error.

When a client attempts to access resources that require
authorization credentials but the client lacks proper authentication
in the request, the server responds with 401.

When a client attempts to access resources with valid
credentials but doesn't have the privilege to perform that action,
the server responds with 403.

The error is mostly returned when the client requests
with either mistyped URL, or the passed resource is moved or deleted,
or the resource doesn't exist.

This error is returned when the client has sent too many,
and has hit the rate limit.

The error is a generic server side error that is
returned for any uncaught and unexpected issues on the server side.
This should be very rare, and you may reach out to us if the problem
persists for a longer duration.

This is an internal error indicating invalid response
received by the client-facing proxy or gateway from the upstream server.

The error is returned for certain routes on a particular
Subnet. This indicates an internal problem with our Subnet node, and may
not necessarily mean the Subnet is down or affected.