Error handling

The Webflow Data API uses standard HTTP status 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 a client-side error (e.g., a problem with the request), and codes in the 5xx range indicate a server-side error.

Error response body

When an error occurs, the API will return a JSON object with the following properties:

PropertyTypeDescription
codestringA machine-readable error code.
messagestringA human-readable error message.
externalReferencestringA link to more information about the error.
detailsarrayAn array of additional error details.

Example error response body:

1{
2 "message": "Requested resource not found: The site cannot be found",
3 "code": "resource_not_found",
4 "externalReference": null,
5 "details": []
6}

Handling rate limit errors

If your application exceeds the rate limit, you will receive a 429 Too Many Requests error. When this happens, you should check the Retry-After header to see how long you should wait before making another request.

The official Webflow SDKs have built-in exponential backoff, which will automatically handle these retries for you. If you are not using one of our SDKs, you should implement your own retry logic.

For more information, see the rate limits documentation.

Common error codes

Status CodeCodeDescription
400bad_requestThe request was malformed.
401not_authorizedThe request lacks valid authentication credentials.
403forbiddenThe authenticated user does not have permissions to perform the requested action.
404resource_not_foundThe requested resource was not found.
409conflictThe request could not be completed due to a conflict with the current state of the resource.
429too_many_requestsThe user has sent too many requests in a given amount of time.
500internal_errorAn unexpected error occurred on our end.