Cryos API documentation - HTTP Codes

When requesting data with Cryos API or other APIs in general, it is not uncommon to experience errors in the form of HTTP codes. In this section we have provided the most relevant and commonly encountered HTTP status codes. For a full list - you can look at https://developer.mozilla.org/en-US/docs/Web/HTTP/Status

  1. 1xx Informational:

    • 100 Continue: The server has received the request headers and the client should proceed to send the request body.

  2. 2xx Success:

    • 200 OK: The request was successful.

    • 201 Created: The request was successful, and a new resource was created.

  3. 4xx Client Errors:

    • 400 Bad Request: The server cannot understand the request due to a client error.

    • 401 Unauthorized: The request requires user authentication.

    • 403 Forbidden: The server understood the request but refuses to authorize it.

    • 404 Not Found: The requested resource could not be found on the server.

    • 429 Too Many request: this is part of the throttling / rate limeter set. You will receive this if you request the API more than 60 times per minute.

  4. 5xx Server Errors:

    • 500 Internal Server Error: A generic error message returned when an unexpected condition was encountered on the server.

    • 503 Service Unavailable: The server is not ready to handle the request. Common causes include a server that is down for maintenance or is overloaded.

Are you experiencing any other HTTP errors besides the most common ones described here - please search for it online either from Microsoft own documentation at xxx or at MDN.