What's New?

We have introduced the following endpoints to support Web Application Firewall Bot Rules:

• Add Bot Rule Set
• Delete Bot Rule Set
• Get All Bot Rule Sets
• Get Bot Rule Set
• Update Bot Rule Set

RTLD endpoints have been updated to introduce support for setting up a profile to deliver log data to:

• Google Cloud Storage
• New Relic (RTLD CDN only)

You may now manage your OAuth 2.0 API clients through the VDMS Identity dashboard.

Learn more.

The following RTLD CDN endpoints have been updated to introduce log data filtering by user agent:

• Add RTLD Configuration
• Get All RTLD Configurations
• Get RTLD Configuration
• Update RTLD Configuration

The following WAF endpoints have been introduced:

• Add Access Rule (ACL)
• Add Custom Rule Set
• Add Managed Rule (Profile)
• Add Rate Rule
• Delete Access Rule (ACL)
• Delete Custom Rule Set
• Delete Managed Rule (Profile)
• Delete Rate Rule
• Get Access Rule (ACL)
• Get All Access Rules (ACL)
• Get All Custom Rule Sets
• Get All Managed Rules (Profiles)
• Get All Rate Rules
• Get All Security Application Manager Configurations (Scopes)
• Get Custom Rule Set
• Get Managed Rule (Profile)
• Get Rate Rule
• Manage All Security Application Manager Configurations (Scopes)
• Update Access Rule (ACL)
• Update Custom Rule Set
• Update Managed Rule (Profile)
• Update Rate Rule

Real-Time Log Delivery now supports multiple profiles, log delivery to Datadog, custom log data, and formatting log data as a JSON array or lines when delivering to either web server(s), AWS S3, or an Azure Block Blob. The following endpoints have been updated to reflect these new capabilities:

• Add RTLD Configuration
• Get All RTLD Configurations
• Get Log Delivery Methods
• Get RTLD Configuration
• Update RTLD Configuration

The following endpoints, which return configuration propagation status, have been introduced:

• Get Customer Origin Status
• Get Deploy Request Status (Rules Engine version 4)
• Get Edge CNAME Status

User privileges are now enforced on REST API requests. Please ensure that the user associated with your REST API token has been granted sufficient permissions to perform the equivalent action within the TCC.

The following endpoints have been updated to support tracking CDN traffic on a per edge CNAME basis via Custom Reports:

• Add Edge CNAME
• Get All Edge CNAMEs
• Get Edge CNAME
• Update Edge CNAME

The Get Billing Usage Data endpoint returns billing usage data for a given month. This data may be filtered by region, country, or POP.

The Get CDN IP Blocks endpoint retrieves a list of IPv4 and IPv6 blocks used by our CDN service.

The following cache-related endpoints are now available:

• Bulk Load Content
• Bulk Purge Content
• Get Bulk Load Request
• Get Bulk Purge Request

The response for the Get Event Log Entries endpoint now includes the unique ID assigned to the event. This ID is reported through the Event ID parameter. This ID may be passed to the Get Event Log Entry endpoint to retrieve information about that event.

The Get Current Edge CNAME Statistics II endpoint retrieves edge CNAME-specific statistics and indicates the date/time for which data was retrieved.

The Get Load Request endpoint provides status information on a load request submitted via the Load Content endpoint.

A response body parameter was added to the Load Content endpoint. This parameter indicates the unique ID assigned to a request to load content.

All Defend endpoints have been modified to return the following status codes:

• 400 Bad Request: Indicates that an invalid date range was requested.
• 404 Not Found: Indicates that the requested object does not exist or is invalid for your customer account.

The response for the Update Configuration endpoint now conforms to JSON standards.