REST API possible errors

Uploadcare uses conventional HTTP response codes to indicate whether an API request was a success or failure. In general, response codes in the 2xx range indicate a request was a success, while codes in the 4xx range indicate errors caused by providing Uploadcare with invalid parameters, etc. Codes within the 5xx range are rare and indicate errors with Uploadcare servers.

HTTP CodeDescription
200 — OKEverything worked as expected.
400 — Bad RequestA request wasn’t accepted, often due to missing parameters.
401 — UnauthorizedNo valid API key provided.
403 — ForbiddenAccess to resource is denied.
404 — Not FoundThe requested resource doesn’t exist.
405 — Method not allowedRequest method not supported, e.g. when using POST instead of GET.
429 — Too Many RequestsRequest was throttled. Expected available in {wait} second.
500, 502, 503, 504 — Server ErrorsSomething went wrong on our side (these are rare.)

Each of the API error responses, except for the 5xx server errors, provides a JSON object holding the detail key with detailed info about an error. Here is an example,

Request:

curl https://api.uploadcare.com/files/

Response:

{"detail": "Authentication credentials were not provided."}

For more information about errors which may occur when addressing particular resources, please read their respective sections.

We’re always happy to help with code, integration, and other stuff. Search our site for more info or post your question in our Community Area.