Index of all API Endpoints
This page contains a categorized list of the API endpoints provided by Fastly, all in one place. Click an endpoint or use the links below each heading to jump to the reference material for that item.
Get information on current and past bills.
|Get an invoice|
|Get an invoice|
|Get month-to-date billing estimate|
A billing address is used to calculate your bill correctly.
A Customer Contact is the base object that holds the different types of contact information Fastly uses to contact a customer.
A Customer is the base object that owns your Users and Services. Some information may be limited depending on access level.
Event logs are used to audit actions performed by customers.
Invitations allow superusers and engineers to invite users to set up accounts as collaborators under a main customer account. Superusers can invite collaborators and assign them any role or permission level on a per-service basis. Engineers with no per-service limitations on their role can only invite new collaborators but cannot modify their permissions.
A list of available permissions that can be assigned to a custom role.
A role is a collection of permissions that can be assigned to a user group.
|Create a role|
|Get a role|
|Delete a role|
|Update a role|
|List permissions in a role|
|Add permissions to a role|
|Remove permissions from a role|
A service authorization allows limited users to access only specified services.
|Show service authorization|
|Delete service authorization|
|Update service authorization|
|List service authorizations|
|Create service authorization|
|Delete service authorizations|
|Update service authorizations|
A service group is a collection of services that can be assigned to a user group.
|List service groups|
|Create a service group|
|Get a service group|
|Delete a service group|
|Update a service group|
|List services to a service group|
|Add services in a service group|
|Remove services from a service group|
A star allows users to mark services of interest.
A user of the Fastly API and web interface. A user is always associated with a customer. Some information may be limited depending on access level.
A user group is a collection of users with service groups and roles.
|List user groups|
|Create a user group|
|Get a user group|
|Delete a user group|
|Update a user group|
|List roles in a user group|
|Add roles to a user group|
|Remove roles from a user group|
|List service groups in a user group|
|Add service groups to a user group|
|Remove service groups from a user group|
|List members of a user group|
|Add members to a user group|
|Remove members of a user group|
An access control list or "ACL" specifies individual IP addresses or subnet ranges and can be accessed and used from Fastly VCL.
|Create a new ACL|
|Describe an ACL|
|Update an ACL|
|Delete an ACL|
An ACL entry holds an individual IP address or subnet range and is a member of an ACL. ACL entries are versionless, which means they can be created, modified, or deleted without activating a new version of your service.
|List ACL entries|
|Update multiple ACL entries|
|Describe an ACL entry|
|Delete an ACL entry|
|Update an ACL entry|
|Create an ACL entry|
An API Token is used to identify who the API call is made on behalf of. It can also be used to restrict what an app can do through authorization scope. Users can create multiple tokens to suit their needs.
A Dictionary is a VCL data table that stores key-value pairs accessible to VCL during request processing. New, empty dictionaries can be attached to a draft version of a service, which must be activated for the dictionary to be included in VCL. Once installed, a dictionary's items may be updated via API calls without having to activate a new version of the associated service configuration. To remove a dictionary, delete it on a draft version of a service (one that is not locked and not active). Once removed, activate the draft service version without the dictionary.
|List edge dictionaries|
|Create an edge dictionary|
|Get an edge dictionary|
|Update an edge dictionary|
|Delete an edge dictionary|
Dictionary Info is a set of metadata describing properties of a dictionary which change as items are added and removed.
|Get edge dictionary metadata|
A Dictionary Item is a single key-value pair that makes up an entry in a Dictionary. Dictionary Items can be added, removed and modified without activating a new version of the associated service.
|List items in an edge dictionary|
|Update multiple entries in an edge dictionary|
|Get an item from an edge dictionary|
|Insert or update an entry in an edge dictionary|
|Delete an item from an edge dictionary|
|Update an entry in an edge dictionary|
|Create an entry in an edge dictionary|
Configuration sets are used to view and select the available versions of the Fastly WAF rules.
|List configuration setsDeprecated|
|List WAFs currently using a configuration setDeprecated|
|Apply a configuration set to a WAFDeprecated|
Firewall object used when configuring WAF.
|Create a firewallDeprecated|
|Get a firewallDeprecated|
|Update a firewallDeprecated|
|Disable a firewallDeprecated|
|Enable a firewallDeprecated|
|List active firewallsDeprecated|
|Get a firewall objectDeprecated|
OWASP settings object used when configuring WAF.
Rules used when configuring WAF.
A Rule status represents the status of a particular rule for a given firewall. For a rule to be attached to a particular firewall and performing any actions, a rule status must exist.
|List rule statusesDeprecated|
|Create or update status of a tagged group of rulesDeprecated|
|Get the status of a rule on a firewallDeprecated|
|Update the status of a ruleDeprecated|
Retrieve the currently deployed WAF ruleset VCL and the date it was deployed.
|Get a WAF rulesetDeprecated|
|Update a WAF rulesetDeprecated|
|Generate WAF ruleset VCLDeprecated|
Tags for categorizing WAF rules. Tags can be filtered by name.
|List WAF tagsDeprecated|
Update status indicates the status of an asynchronous process for updating a firewall object.
|List update statusesDeprecated|
|Get the status of a WAF updateDeprecated|
Maps and relates backends as belonging to directors. Backends can belong to any number of directors but directors can only hold one reference to a specific backend.
|Get a director-backend relationship|
|Create a director-backend relationship|
|Delete a director-backend relationship|
A Director is responsible for balancing requests among a group of Backends. In addition to simply balancing, Directors can be configured to attempt retrying failed requests. Additionally, Directors have a quorum setting which can be used to determine when the Director as a whole is considered "up", in order to prevent "server whack-a-mole" following an outage as servers come back up. Only directors created via the API can be modified via the API. Directors known as "autodirectors" that are created automatically when load balancing groups of servers together cannot be modified or retrieved via the API.
|Create a director|
|Get a director|
|Update a director|
|Delete a director|
A pool is responsible for balancing requests among a group of servers. In addition to balancing, pools can be configured to attempt retrying failed requests. Pools have a quorum setting that can be used to determine when the pool as a whole is considered up, in order to prevent problems following an outage as servers come back up.
|List server pools|
|Create a server pool|
|Get a server pool|
|Update a server pool|
|Delete a server pool|
A server is an address (IP address or hostname) to which the Fastly Load Balancer service can forward requests. This service can define multiple servers and assign it to a pool. Fastly can then select any one of these servers based on a selection policy defined for the pool.
|List servers in a pool|
|Get a pool server|
|Update a server|
|Delete a server from a pool|
|Add a server to a pool|
Microsoft Azure Blob Storage
Fastly will upload log messages to the Azure Blob Storage container in the format specified in the Azure Blob object.
|List Azure Blob Storage log endpoints|
|Create an Azure Blob Storage log endpoint|
|Get an Azure Blob Storage log endpoint|
|Update an Azure Blob Storage log endpoint|
|Delete the Azure Blob Storage log endpoint|
Fastly will upload log messages to the Google BigQuery dataset and table in the format specified in the BigQuery logging object.
|List BigQuery log endpoints|
|Create a BigQuery log endpoint|
|Get a BigQuery log endpoint|
|Update a BigQuery log endpoint|
|Delete a BigQuery log endpoint|
Fastly will upload log messages to your Rackspace Cloud Files account.
|List Cloud Files log endpoints|
|Create a Cloud Files log endpoint|
|Get a Cloud Files log endpoint|
|Update the Cloud Files log endpoint|
|Delete the Cloud Files log endpoint|
Fastly will upload log messages to Datadog in the format specified in the Datadog configuration object.
|List Datadog log endpoints|
|Create a Datadog log endpoint|
|Get a Datadog log endpoint|
|Update a Datadog log endpoint|
|Delete a Datadog log endpoint|
Fastly will upload log messages to the DigitalOcean Space in the format specified in the DigitalOcean Spaces object.
|List DigitalOcean Spaces log endpoints|
|Create a DigitalOcean Spaces log endpoint|
|Get a DigitalOcean Spaces log endpoint|
|Update a DigitalOcean Spaces log endpoint|
|Delete a DigitalOcean Spaces log endpoint|
Fastly will upload log messages periodically to the server in the format specified in the Elasticsearch object.
|List Elasticsearch log endpoints|
|Create an Elasticsearch log endpoint|
|Get an Elasticsearch log endpoint|
|Update an Elasticsearch log endpoint|
|Delete an Elasticsearch log endpoint|
Fastly will upload log messages periodically to the server in the format specified in the FTP object.
|List FTP log endpoints|
|Create an FTP log endpoint|
|Get an FTP log endpoint|
|Update an FTP log endpoint|
|Delete an FTP log endpoint|
Fastly will upload log messages to the GCS bucket in the format specified in the GCS object.
|List GCS log endpoints|
|Create a GCS log endpoint|
|Get a GCS log endpoint|
|Update a GCS log endpoint|
|Delete a GCS log endpoint|
Google Cloud Pub/Sub Logging
Fastly will publish log messages to a Google Cloud Pub/Sub topic in the format specified in the Pub/Sub logging object.
|List GCP Cloud Pub/Sub log endpoints|
|Create a GCP Cloud Pub/Sub log endpoint|
|Get a GCP Cloud Pub/Sub log endpoint|
|Update a GCP Cloud Pub/Sub log endpoint|
|Delete a GCP Cloud Pub/Sub log endpoint|
Fastly will stream log messages to the Heroku account in the format specified in the Heroku object.
|List Heroku log endpoints|
|Create a Heroku log endpoint|
|Get a Heroku log endpoint|
|Update the Heroku log endpoint|
|Delete the Heroku log endpoint|
Fastly will upload log messages to Honeycomb.io in the format specified in the Honeycomb object.
|List Honeycomb log endpoints|
|Create a Honeycomb log endpoint|
|Get a Honeycomb log endpoint|
|Update a Honeycomb log endpoint|
|Delete the Honeycomb log endpoint|
Fastly will upload log messages to an HTTPS endpoint in the format specified in the HTTPS object. The HTTPS endpoint requires proof of domain ownership before logs can be received. Learn how to validate your domain in our HTTPS endpoint documentation.
|List HTTPS log endpoints|
|Create an HTTPS log endpoint|
|Get an HTTPS log endpoint|
|Update an HTTPS log endpoint|
|Delete an HTTPS log endpoint|
Fastly will upload log messages periodically to the server in the format specified in the Kafka object.
|List Kafka log endpoints|
|Create a Kafka log endpoint|
|Get a Kafka log endpoint|
|Update the Kafka log endpoint|
|Delete the Kafka log endpoint|
Fastly will publish log messages to an Amazon Kinesis stream in the format specified in the Amazon Kinesis Data Streams logging object.
|List Amazon Kinesis log endpoints|
|Create an Amazon Kinesis log endpoint|
|Get an Amazon Kinesis log endpoint|
|Update the Amazon Kinesis log endpoint|
|Delete the Amazon Kinesis log endpoint|
Fastly will stream log messages to the Logentries account in the format specified in the Logentries object.
|List Logentries log endpoints|
|Create a Logentries log endpoint|
|Get a Logentries log endpoint|
|Update a Logentries log endpoint|
|Delete a Logentries log endpoint|
Fastly will stream log messages to the Loggly account in the format specified in the Loggly logging object.
|List Loggly log endpoints|
|Create a Loggly log endpoint|
|Get a Loggly log endpoint|
|Update a Loggly log endpoint|
|Delete a Loggly log endpoint|
Fastly will upload log messages to the Log Shuttle bucket in the format specified in the logshuttle object.
|List Log Shuttle log endpoints|
|Create a Log Shuttle log endpoint|
|Get a Log Shuttle log endpoint|
|Update a Log Shuttle log endpoint|
|Delete a Log Shuttle log endpoint|
New Relic Logs
Fastly will upload log messages to New Relic Logs in the format specified in the New Relic configuration object.
|List New Relic log endpoints|
|Create a New Relic log endpoint|
|Get a New Relic log endpoint|
|Update a New Relic log endpoint|
|Delete a New Relic log endpoint|
Fastly will upload log messages to the OpenStack bucket in the format specified in the openstack object.
|List OpenStack log endpoints|
|Create an OpenStack log endpoint|
|Get an OpenStack log endpoint|
|Update an OpenStack log endpoint|
|Delete an OpenStack log endpoint|
Fastly will stream log messages to the Papertrail account in the format specified in the Papertrail object.
|List Papertrail log endpoints|
|Create a Papertrail log endpoint|
|Get a Papertrail log endpoint|
|Update a Papertrail log endpoint|
|Delete a Papertrail log endpoint|
Fastly will upload log messages to the S3 bucket in the format specified in the S3 object.
|List AWS S3 log endpoints|
|Create an AWS S3 log endpoint|
|Get an AWS S3 log endpoint|
|Update an AWS S3 log endpoint|
|Delete an AWS S3 log endpoint|
Fastly will stream log messages to the Scalyr account in the format specified in the Scalyr object.
|List Scalyr log endpoints|
|Create a Scalyr log endpoint|
|Get a Scalyr log endpoint|
|Update the Scalyr log endpoint|
|Delete the Scalyr log endpoint|
Fastly will upload log messages periodically to the server in the format specified in the SFTP object.
|List SFTP log endpoints|
|Create an SFTP log endpoint|
|Get an SFTP log endpoint|
|Update an SFTP log endpoint|
|Delete an SFTP log endpoint|
Fastly will POST messages to your Splunk account in the format specified in the Splunk object.
|List Splunk log endpoints|
|Create a Splunk log endpoint|
|Get a Splunk log endpoint|
|Update a Splunk log endpoint|
|Delete a Splunk log endpoint|
Fastly will POST messages to the Sumo Logic account in the format specified in the Sumologic object.
|List Sumologic log endpoints|
|Create a Sumologic log endpoint|
|Get a Sumologic log endpoint|
|Update a Sumologic log endpoint|
|Delete a Sumologic log endpoint|
Fastly will stream log messages to the location in the format specified in the Syslog object.
|List Syslog log endpoints|
|Create a syslog log endpoint|
|Get a syslog log endpoint|
|Update a syslog log endpoint|
|Delete a syslog log endpoint|
Domain Inspector Historical API
Domain Inspector provides a JSON-formatted historical API for visibility into responses delivered from your domains by Fastly. The API offers a standardized set of data to report in minutely, hourly, or daily granularity on every domain response, byte, and status code received by a specified service.
|Get historical domain data for a service|
Domain Inspector Real-time API
The real-time domain metrics API allows you to programmatically retrieve per-domain delivery metrics derived from your Fastly services in one-second periods up to the last complete second.
The Historical Stats API allows you to programmatically retrieve historical caching statistics derived from your Fastly services. You can use these metrics to help you optimize your site’s data caching and analyze your site’s traffic.
|Get historical stats|
|Get historical stats for a single field|
|Get aggregated historical stats|
|Get historical stats for a single service|
|Get historical stats for a single service/field combination|
|Get usage statistics|
|Get usage statistics per service|
|Get month-to-date usage statistics|
|Get region codes|
Origin insights is a real-time JSON-formatted data stream providing visibility into responses delivered from your origin servers to Fastly. The API offers a standardized set of data to report in real-time every origin response, byte, and status code received by a specified service in one-second periods up to the last complete second.
|Get real-time origin data from specified time|
|Get real-time origin data for the last 120 seconds|
|Get a limited number of real-time origin data entries|
Origin Inspector Historical API
Origin Inspector provides a JSON-formatted historical API for visibility into responses delivered from your origin servers to Fastly. The API offers a standardized set of data to report in minutely, hourly or daily granularity on every origin response, byte, and status code received by a specified service.
|Get historical origin data for a service|
Origin Inspector Real-time API
Origin Inspector offers a real-time JSON-formatted data stream providing visibility into responses delivered from your origin servers to Fastly. The API offers a standardized set of data to report in real-time every origin response, byte, and status code received by a specified service in one-second periods up to the last complete second.
The real-time analytics API offers a standardized set of data about traffic received by a specified service in one-second time periods up to the last complete second.
Stats give you information on the usage and performance of your Service. They can be requested by Service and over a particular time span. Stats are broken down per POP, giving you information on how your Services are being used across the world. There is now a more flexible, and fully featured Stats API available.
|Get stats for a service|
An object store is a persistent, globally consistent key-value store accessible to Compute@Edge services during request processing.
Instant Purging removes content from Fastly immediately so it can be refreshed from your origin servers. The main entry point for the API,
https://api.fastly.com/, is not needed for an individual URL Instant Purge.
A backend (also sometimes called an origin server) is a server identified by IP address or hostname, from which Fastly will fetch your content. There can be multiple backends attached to a service, but each backend is specific to one service. By default, the first backend added to a service configuration will be used for all requests (provided it meets any conditions attached to it). If multiple backends are defined for a service, the first one that has no attached conditions, or whose condition is satisfied for the current request, will be used, unless that behavior is modified using the
auto_loadbalancefield described below.
|Create a backend|
|Describe a backend|
|Update a backend|
|Delete a backend|
A domain represents the domain name through which visitors will retrieve content. There can be multiple domains for a service.
|Validate DNS configuration for all domains on a service|
|Validate DNS configuration for a single domain on a service|
|Add a domain name to a service|
|Describe a domain|
|Update a domain|
|Remove a domain from a service|
A domain ownership is the record that Fastly keeps after a customer has validated control over a domain.
Healthchecks are used to customize the way Fastly checks on your Backends. If an origin server is marked unhealthy due to health checks, Fastly will stop attempting to send requests to it. If all origin servers are marked unhealthy, Fastly will attempt to serve stale. If no stale object is available, a 503 will be returned to the client.
|Create a healthcheck|
|Get a healthcheck|
|Update a healthcheck|
|Delete a healthcheck|
Compute@Edge is a computation platform capable of running custom binary packages that you compile on your own systems and upload to Fastly. These packages are associated with a service version and are deployed to Fastly's edge network.
A resource represents a link between a resource type and a service version.
|Create a resource|
|Display a resource|
|Update a resource|
|Delete a resource|
A Service represents the configuration for a website, app, API, or anything else to be served through Fastly. A Service can have many Versions, through which Backends, Domains, and more can be configured.
|Create a service|
|Get service details|
|Search for a service by name|
|Get a service|
|Update a service|
|Delete a service|
|List the domains within a service|
A Version represents a specific instance of the configuration for a service. A Version can be cloned, locked, activated, or deactivated.
|List versions of a service|
|Create a service version|
|Get a version of a service|
|Update a service version|
|Validate a service version|
|Activate a service version|
|Deactivate a service version|
|Clone a service version|
|Lock a service version|
Customers with access to multiple sets of IP pools are able to apply different configuration options to their TLS enabled domains.
|List TLS activations|
|Enable TLS for a domain using a custom certificate|
|Get a TLS activation|
|Disable TLS on a domain|
|Update a certificate|
A TLS certificate is used to terminate TLS traffic for one or more of your TLS domains.
TLS domains are all the domains (including wildcard domains) included in any TLS certificate's Subject Alternative Names (SAN) list. Included in the response is information about which certificates reference this domain as well as the TLS activation indicating which certificate is enabled to serve TLS traffic for the domain.
|List TLS domains|
A private key is used to sign a Certificate. A key can be used to sign multiple certificates.
Setting and Unsetting Mutual TLS on TLS Activations
Mutual TLS can be added to existing TLS activations to allow for client-to-server authentication. In order to use mutual TLS, you must already have active server-side TLS using either custom certificates or an enabled Fastly-managed subscription.
Managing and Uploading Mutual Authentications
The Mutual TLS API allows for client-to-server authentication using client-side X.509 authentication. The main Mutual Authentication object represents the certificate bundle and other configurations which support Mutual TLS for your domains.
|List Mutual Authentications|
|Create a Mutual Authentication|
|Get a Mutual Authentication|
|Delete a Mutual TLS|
Available to Platform TLS customers, these endpoints streamline the upload, deployment and management of large numbers of TLS certificates. A certificate is used to terminate TLS traffic for one or more of your fully qualified domain names (domains). Uploading a new certificate automatically enables TLS for all domains listed as Subject Alternative Names (SAN entries) on the certificate.
The TLS subscriptions API allows you to programmatically generate TLS certificates that are procured and renewed by Fastly. Once a subscription is created for a given hostname or wildcard domain, DNS records are checked to ensure that the domain on the subscription is owned by the subscription creator. Provided DNS records are maintained, TLS certificates will automatically renew.
|List TLS subscriptions|
|Create a TLS subscription|
|Get a TLS subscription|
|Delete a TLS subscription|
|Update a TLS subscription|
|Creates a GlobalSign email challenge|
|Delete a GlobalSign email challenge|
Check content status
Fastly makes it possible to see which version of a particular URL is cached on each edge server.
|Check status of content in each POP's cache|
See the line-by-line changes in configuration between two different versions of a service.
|Diff two service versions|
Documentation of the endpoints that return the Fastly API Documentation.
Public IP List
To help you manage firewall rules for connections from Fastly to your origin, we provide access to the list of Fastly's assigned IP ranges. Changes to this list will be announced in advance as an "IP address announcement" (example) along with other service announcements to our status page, which you can subscribe to. This list is exhaustive and includes all Fastly-owned IP ranges, so any client connections, log streaming reports, and origin connections should use these addresses.
|List Fastly's public IPs|
Supports redirecting traffic for apex domains, subdomains, or wildcard domains to a WWW subdomain.
|List apex redirects|
|Create an apex redirect|
|Get an apex redirect|
|Update an apex redirect|
|Delete an apex redirect|
Configures cache lifetime for objects stored in the Fastly cache, overriding cache freshness information that would otherwise be determined from cache-related headers on the HTTP response. When used in conjunction with conditions, cache settings objects provide detailed control over how long content persists in the cache.
|List cache settings objects|
|Create a cache settings object|
|Get a cache settings object|
|Update a cache settings object|
|Delete a cache settings object|
Conditions are used to control whether logic defined in configured VCL objects is applied for a particular client request. A condition contains a VCL conditional expression that evaluates to either true or false and is used to determine whether the condition is met. The type of the condition determines where it is executed and the VCL variables that can be evaluated as part of the conditional logic.
|Create a condition|
|Describe a condition|
|Update a condition|
|Delete a condition|
Compare the changes in generated VCL between two versions of a service. This is sometimes called a "diff" because the comparison may highlight "differences" between the versions. To compare the configuration changes between two versions of a service represented in YAML format instead, use the related diff endpoint.
|Get a comparison of the VCL changes between two service versions|
Gzip configuration allows you to choose resources to automatically compress.
|List gzip configurations|
|Create a gzip configuration|
|Get a gzip configuration|
|Update a gzip configuration|
|Delete a gzip configuration|
Header objects are used to add, modify, or delete headers from requests and responses. The header content can be simple strings or be derived from variables inside Varnish. Regular expressions can be used to customize the headers even further.
|List Header objects|
|Create a Header object|
|Get a Header object|
|Update a Header object|
|Delete a Header object|
Rate limiters add configurable origin request rate limiting to a service. This information is part of a limited availability release. For more information, see our product and feature lifecycle descriptions. To use this feature you must purchase a Premier Platform subscription for either Signal Sciences Cloud WAF or Signal Sciences Next-Gen WAF and have a paid account with a contract for full-site delivery.
|List rate limiters|
|Create a rate limiter|
|Get a rate limiter|
|Update a rate limiter|
|Delete a rate limiter|
Settings used to customize Fastly's request handling. When used with Conditions the Request Settings object allows you to fine tune how specific types of requests are handled.
|List Request Settings objects|
|Create a Request Settings object|
|Get a Request Settings object|
|Update a Request Settings object|
|Delete a Request Settings object|
Allows you to create synthetic responses that exist entirely on the varnish machine. Useful for creating error or maintenance pages that exists outside the scope of your backend architecture. Best when used with Condition objects.
|List Response objects|
|Create a Response object|
|Get a Response object|
|Update a Response object|
|Delete a Response Object|
Handles default settings for a particular version of a service.
VCL Snippets are blocks of VCL logic inserted into your service's configuration that don't require custom VCL.
|Get a dynamic snippet|
|Update a dynamic snippet|
|Create a snippet|
|Get a versioned snippet|
|Update a versioned snippet|
|Delete a snippet|
A VCL is a Varnish configuration file used to customize the configuration for a Service.
|List custom VCL files|
|Create a custom VCL file|
|Get boilerplate VCL|
|Get a custom VCL file|
|Update a custom VCL file|
|Delete a custom VCL file|
|Get a custom VCL file with syntax highlighting|
|Download a custom VCL file|
|Get the generated VCL for a service|
|Get the generated VCL with syntax highlighting|
|Set a custom VCL file as main|
A firewall represents a configuration of a Web Application Firewall (WAF) on a service. A firewall has many firewall versions through which you can manage rules.
Firewall version objects contain all of the rules and settings for your WAF and remain empty until properly configured. To understand the behavior of thresholds and scores, see Managing rules. Newly created firewall versions are initiated without any associated rules. See Active Rules for details. Changes to your WAF's rules and settings can be made by cloning an existing firewall version, making the changes, and then activating the new firewall version.
|List firewall versionsDeprecated|
|Create a firewall versionDeprecated|
|Get a firewall versionDeprecated|
|Update a firewall versionDeprecated|
|Clone a firewall versionDeprecated|
|Deploy or activate a firewall versionDeprecated|
Rules are universally available for every firewall. Rules can have one or multiple rule revisions. You can add rules to your firewall by creating active rules.
|List active rules on a WAFDeprecated|
|Add a rule to a WAF as an active ruleDeprecated|
|Delete multiple active rules from a WAFDeprecated|
|Get an active WAF rule objectDeprecated|
|Delete an active ruleDeprecated|
|Update an active ruleDeprecated|
|Update multiple active rulesDeprecated|
|Create active rules by tagDeprecated|
WAF Rule Exclusions
WAF rule exclusions provide a flexible way to handle false positives, allowing specific variables, rules, and the entire WAF to be excluded on a per request basis. You can configure up to 300 WAF exclusions and each exclusion of type
rulecan have up to 30 rules associated with it.
|List WAF rule exclusionsDeprecated|
|Create a WAF rule exclusionDeprecated|
|Get a WAF rule exclusionDeprecated|
|Delete a WAF rule exclusionDeprecated|
|Update a WAF rule exclusionDeprecated|
Rule revisions track new variations of rules as they change over time with enhancements, fixes, and improvements. This object allows you to find a specific variation of a rule for use in your application. An active rule on a firewall uses a specific rule revision.
|List revisions for a ruleDeprecated|
|Get a revision of a ruleDeprecated|