Introduction

Our API has predictable, resource-oriented URLs and uses HTTP response codes to indicate API errors. We use built-in HTTP features, such as HTTP authentication and HTTP terminology, which can be understood by HTTP clients. JSON will be returned in all responses from the API, including errors.

Responses

The API uses HTTP response codes to show success or failure of an API request. In general, 2xx codes indicate success, 4xx codes indicate an error that resulted from the provided information (e.g. a required parameter is missing or invalid, etc.), and codes in the 5xx range indicate an error connected with our servers.

Maximum Body Request

Maximum API body request size is 1MB.

HTTP Status Code Summary

Code	Description
2xx	OK — Request has been completed successfully.
400	Bad Request — Required parameter is missing.
401	Unauthorized — Provided credentials are invalid or your API token has expired.
403	Forbidden — Access denied. You do not have enough rights.
404	Not Found — Requested item doesn't exist.
429	Too Many Requests — You have exceeded the number of allowed requests for your resources.
503	Service Unavailable — You have made a mistake in request parameters or the service is currently unavailable.
500 502 504	Server errors — Something went wrong on our end.

Rate limits

There is a general limit of 4 requests per second. If you go over the rate limit, you will receive a message.

Prefetch Calls Limiting

You can make 1 prefetch request for a resource per minute. One prefetch request is limited to 100 patterns. If you go over the rate limit, you will receive a message.

Purge Calls Limiting

We have different limits for purge by pattern and purge by URL.

For purge by URL you can make two purge request for a resource per minute. One purge request is limited to 100 URLs. If you go over the rate limit, you will receive a message.

Overview CDN

Introduction#

Responses#

Maximum Body Request#

HTTP Status Code Summary#

Rate limits#

Prefetch Calls Limiting#