---
title: Errors
description: Storyblok's API relies on standard HTTP response codes to signal the outcome of requests.
url: https://storyblok.com/docs/api/management/getting-started/errors
---

# Errors

Storyblok uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the `2xx` range indicate success. Codes in the `4xx` range indicate an error that failed given the information provided (e.g., a required parameter was omitted, a charge failed, content entry was not published but version requested was set to published, etc.). Codes in the `5xx` range indicate an error with Storyblok’s servers (these are rare).

Some `4xx` errors that could be handled programmatically (e.g., content entry was not found) include an error code that briefly explains the error reported.

## HTTP status code summary

| Code | Description |
| --- | --- |
| 200 - OK | Everything worked as expected. |
| 400 - Bad Request | The wrong format was sent (e.g., XML instead of JSON). |
| 401 - Unauthorized | No valid API key was provided. |
| 404 - Not Found | The requested resource doesn’t exist (e.g., due to not yet published content entries). |
| 422 - Unprocessable Entity | The request was unacceptable, often due to missing a required parameter. |
| 429 - Too Many Requests | Too many requests hit the API too quickly. We recommend an exponential backoff of your requests. |
| 500, 502, 503, 504 - Server Errors | Something went wrong on Storyblok’s end (these errors are rare). |

## Pagination

-   [Previous: Authentication](/docs/api/management/getting-started/authentication)
-   [Next: Organization](/docs/api/management/getting-started/organization)