The 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.
IMPORTANT: On May 8, 2018 the Fastly API will require TLS 1.2. Due to the PCI Security Standards Council mandate, TLS versions 1.0 and 1.1 will no longer be supported across Fastly's infrastructure. For more information, see our guide on verifying TLS 1.2 support.
Interactive clients for the Fastly API are available in a variety of languages. Check our Clients page for more information on each.
Read our Authentication page to learn about how to provide your credentials when calling the Fastly API.
You can make up to 1,000 non-read requests per hour. The limit is per user tied to your API token. Read requests, such as
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.
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.