DocumentationThe Fastly API is a RESTful API that supports all features available through the Fastly web interface. Use the libraries below to guide the development of your sites and applications.
Account |
Configuration |
Purging |
Historical Stats |
Remote Logging |
IMPORTANT: The Fastly API requires TLS 1.2. Because of the PCI Security Standards Council mandate, TLS versions 1.0 and 1.1 are no longer supported for accessing Fastly's API.
Clients
Clients for the Fastly API are available in a variety of languages. Check our Clients page for more information on each.
Authentication
Read our Authentication page to learn about how to provide your credentials when calling the Fastly API.
Rate limiting
You can make up to 1,000 non-read requests per hour. The limit is applied to the authenticated user making the request. Read requests, such as GET and HEAD requests, are not limited. Surrogate key and URL purge requests are also not limited, but purge all requests count against the per-hour rate limit. If you go over the rate limit, you will receive a 429 Too Many Requests HTTP response.
Response headers
Fastly provides rate limit information in the response header, as shown in the example below. The Fastly-RateLimit-Remaining header provides the number of API requests remaining in the current rate limit window. The Fastly-RateLimit-Reset provides the time at which the current rate limit window resets in UTC epoch seconds.