No entries match these filters. Clear filters
iOS SDK for URLSession 1.0.0 (2026-11-20)
Nov 20, 2026
·
issue 146
DataDome adds an iOS SDK for URLSession with challenge-aware request retries and full async/await, Combine, and completion-handler support︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
New ProtectedURLSession class supports data, upload, download, and bytes task types for intercepting and protecting URLSession traffic on iOS.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Challenges returned by a redirect destination are retried at that destination, matching URLSession's redirected-request behaviour. Not checked yet Supports async/await, completion handlers, and Combine as calling conventions for all protected request types. Not checked yet
3 details in Everything
Go module 2.6.0 (2026-11-19)
Nov 19, 2026
·
issue 144
DataDome Go module now truncates headers lists at 768 bytes, up from 512︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
DataDome's Go module now truncates the HeadersList at 768 bytes instead of 512, allowing more header data to be forwarded for bot-detection analysis.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 more in Everything
Cloudflare Worker Rust module 1.1.0 (2026-11-19)
Nov 19, 2026
·
issue 144
DataDome: Cloudflare Worker Rust module raises the HeadersList truncation limit from 512 to 768 bytes, so large header sets are less likely cut short.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Envoy module 2.9.0 (2026-11-19)
Nov 19, 2026
·
issue 144
DataDome: Raises the HeadersList truncation limit from 512 to 768 bytes, allowing more header data to be passed through without being cut off.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Fastly module 3.2.1 (2026-11-18)
Nov 18, 2026
·
issue 144
DataDome's Fastly module adds waf.inspection.disabled to skip Next-Gen WAF WAF A reverse proxy that inspects HTTP/HTTPS traffic and blocks requests matching known attack patterns such as SQL injection or XSS, sitting between clients and a web application to filter malicious input before it reaches the server. inspection on out-of-band Protection API requests︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
React Native SDK for Axios 4.0.0 (2026-11-17)
Nov 17, 2026
·
issue 143
DataDome React Native SDK for Axios 4.0.0 adds native challenge display, DataDomeInterceptor.attach() , and full Axios adapter coverage including the fetch adapter︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Protect all requests on a custom Axios instance so every outbound call is covered by DataDome bot detection.
javascript
copy
import axios from 'axios';
import { DataDome, DataDomeInterceptor } from '@datadome/react-native-datadome-axios';
const dataDome = new DataDome({ clientKey: '<your-client-key>' });
const instance = axios.create({ baseURL: 'https://api.example.com' });
DataDomeInterceptor.attach(instance);
// Later, when tearing down:
DataDomeInterceptor.eject(instance);
Read the DataDome cookie for a specific URL after a challenge is solved, e.g. to forward it to a server-side session.
javascript
copy
const cookie = await dataDome.getCookie('https://api.example.com/endpoint');
console.log(cookie);
Attach DataDome protection to any Axios instance — default or custom — with DataDomeInterceptor.attach(instance) and remove it with DataDomeInterceptor.eject(instance) .︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Configure the SDK with new DataDome({ clientKey }) , passing an optional domain, replacing the previous multi-step setup. Not checked yet Protect requests across all Axios adapter types — default, instance-level, or per-request — including the fetch adapter via a custom env.fetch. Not checked yet Display challenges natively without adding any component to the view hierarchy, powered by @datadome/react-native-core-datadome. Not checked yet Automatically retry a request after a solved challenge from the request's adapter, so interceptors and transforms run only once per request regardless of retry count. Not checked yet
+3 more
show less
Export DataDome, ResponseValidationStatus, DataDomeConfiguration, and DataDomeCookie types from the @datadome/react-native-core-datadome core SDK. Not checked yet Drop the react-native-webview peer dependency — apps that do not otherwise use it can now uninstall it. Not checked yet Retrieve a stored cookie with dataDome.getCookie(url) , replacing the old getStoredDataDomeCookie() function. Not checked yet
Attach DataDome protection to any Axios instance — default or custom — with DataDomeInterceptor.attach(instance) and remove it with DataDomeInterceptor.eject(instance) .︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Configure the SDK with new DataDome({ clientKey }) , passing an optional domain, replacing the previous multi-step setup. Not checked yet Display challenges natively without adding any component to the view hierarchy, powered by @datadome/react-native-core-datadome. Not checked yet Export DataDome, ResponseValidationStatus, DataDomeConfiguration, and DataDomeCookie types from the @datadome/react-native-core-datadome core SDK. Not checked yet
4 more in Everything
└──▷ BREAKING ON UPGRADE
! Package renamed from @datadome/datadome-axios to @datadome/react-native-datadome-axios — update all imports and package.json references.! @datadome/react-native-core-datadome (1.0.0+) is now a required peer dependency and must be installed in the application.! Minimum React Native version raised to 0.85+ with the New Architecture required (previously 0.72+); iOS minimum raised to 15.1+ (previously 12+); Android minSdkVersion raised to 24 (previously 21); Axios minimum raised to 1.12+ (previously 1.11+).! DataDome.getInstance() .setSdkKey() , DataDome.configure() , and DataDome.configureWithOrigin() are removed — replace with new DataDome({ clientKey }) .! new DataDomeInterceptor({ axiosInstance }) and the manual interceptor setup with requestAdapter, responseEventHandler, and responseAdapter are removed — replace with new DataDomeInterceptor(dataDome) .attach(instance) .! getStoredDataDomeCookie() and storeCookie() are removed — replace with dataDome.getCookie(url) .! DataDomeModal is removed.! enableVerboseLogs is removed.
DataDome adds custom HTML waiting-room templates to Priority Protect, with live-data variables and a template management API︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Build a branded waiting-room page that shows a visitor's queue position, total queue size, opening date, and support request ID using live Priority Protect variables.
html
copy
<main class="card">
<p>Your position: <strong><span data-priorityprotect-var="position"></span></strong> of <span data-priorityprotect-var="size"></span></p>
<p>Opens on <strong><span data-priorityprotect-var="openingDate"></span></strong></p>
<p><small>Updated <span data-priorityprotect-var="lastUpdateDateTime"></span> · Request ID <span data-priorityprotect-var="requestId"></span></small></p>
</main>
Assign a custom template to a waiting room so visitors see your branding instead of the default DataDome page.
📍 In Priority Protect, go to Priorities, open or create a waiting room, choose Edit, set Template to Custom, select your template, then Save.
Inject live queue data into custom waiting-room pages using data-priorityprotect-var attributes on HTML elements, with supported values position, size, openingDate, lastUpdateDateTime, and requestId.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Create, update, list, and delete custom waiting-room templates through the Priority Protect API. Not checked yet Assign custom HTML templates to Priority Protect waiting rooms, up to 50,000 characters per template, with changes propagating within 1 minute of saving. Not checked yet Show queue position and total visitors inside a data-priorityprotect-var panel element, which Priority Protect hides via a hidden CSS class until data is available. Not checked yet Show the opening date for time-based waiting rooms using data-priorityprotect-var="openingDate" inside a panel element. Not checked yet
+1 more
show less
Expose the visitor's requestId via data-priorityprotect-var="requestId" so support teams can look up sessions in Explore. Not checked yet
6 details in Everything
DataDome adds Priority Protect waiting room configuration with API-driven capacity, admission rate, and direct-access controls︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Create a Time-Based waiting room for a flash sale, admitting 50 visitors per minute with a 30-minute pre-admission window and browser-side validation enabled.
json
copy
{
"name": "Flash Sale Q4",
"priority": 100,
"startAt": "2025-11-28T08:00:00Z",
"endAt": "2025-11-28T12:00:00Z",
"maximumConcurrentVisitors": 500,
"admissionRatePerMinute": 50,
"inactivityTimeoutMinutes": 15,
"preAdmission": { "durationMinutes": 30 },
"matchingCondition": "domain:shop.example.com AND url:/sale*",
"directAccessTrafficType": "Verified bots, Custom rules",
"enforceClientSideValidation": true,
"templateId": "default",
"isEnabled": true
}
Create an Always on waiting room to protect an API checkout endpoint from unexpected traffic spikes, skipping the queue for internal monitoring covered by Bot Protect Allow rules.
json
copy
{
"name": "Checkout Always On",
"priority": 200,
"maximumConcurrentVisitors": 1000,
"admissionRatePerMinute": 100,
"inactivityTimeoutMinutes": 10,
"matchingCondition": "domain:shop.example.com AND (url:/checkout* OR url:/api/checkout*)",
"directAccessTrafficType": "Custom rules",
"enforceClientSideValidation": true,
"isEnabled": true
}
DataDome adds Priority Protect, a virtual waiting room that queues real visitors and blocks bots before they can take a place︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Force every visitor of a test URL into the waiting room immediately by setting Maximum concurrent visitors to 0, so you can verify the page before go-live.
📍 In the DataDome Dashboard, go to Priorities › Create a waiting room. Set Type to Always on , enter your test URL as the Matching Condition, and set Maximum concurrent visitors to 0. Click Create a waiting room .
Protect a flash-sale path so that only 500 visitors browse it at once and 50 new visitors are admitted per minute when capacity frees up.
📍 In the DataDome Dashboard, go to Priorities › Create a waiting room. Set Type to Time-Based , enter domain:shop.example.com AND url:/sale* as the Matching Condition, set Maximum concurrent visitors to 500 and Admission Rate to 50, then set the start and end dates. Click Create a waiting room .
Create a waiting room by going to Dashboard > Priorities and clicking Create a waiting room , choosing Time-Based for a scheduled event or Always on for year-round protection, then setting a name, rank, Maximum concurrent visitors, Admission rate, and a Matching Condition such as domain:shop.example.com AND url:/sale*.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Control waiting room capacity with two settings: Maximum concurrent visitors (how many visitors browse protected pages simultaneously) and Admission rate (how many waiting visitors are admitted per minute). Not checked yet Use a testing token — a secret link parameter — to let your team skip a waiting room during tests without disabling it for real visitors. Not checked yet Support pre-admission periods on time-based waiting rooms so visitors can join the queue before the event start time. Not checked yet Allow verified bots such as search-engine crawlers to skip the waiting room by enabling Direct access > Verified bots. Not checked yet
+1 more
show less
Apply custom branded waiting room pages via custom templates. Not checked yet
6 details in Everything
DataDome adds a React Native Fetch SDK built on CoreDataDome for automatic bot-challenge handling in Fetch API requests︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Wrap all Fetch API calls in a React Native app with DataDome bot protection so challenges are automatically displayed and requests retried.
javascript
copy
import { DataDome, type DataDomeConfiguration, createDataDomeFetch } from '@datadome/react-native-datadome-fetch';
const config: DataDomeConfiguration = {
clientKey: 'YOUR_CLIENT_KEY',
domain: 'https://api.example.com',
};
const dataDome = new DataDome(config);
const protectedFetch = createDataDomeFetch(dataDome);
const response = await protectedFetch('https://api.example.com/items', {
headers: { Accept: 'application/json' },
});
Install the React Native Fetch SDK and its dependency via npm install --save @datadome/react-native-datadome-fetch @datadome/react-native-core-datadome or yarn add @datadome/react-native-datadome-fetch @datadome/react-native-core-datadome.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Configure a DataDomeConfiguration object with clientKey (required) and optional domain to scope the instance to an origin URL, then instantiate DataDome. Not checked yet Create a drop-in Fetch API replacement using createDataDomeFetch, which automatically injects headers, validates responses, displays challenges (Slider, Device Check, or Block page), and retries requests after resolution. Not checked yet Supports React Native 0.85+ with New Architecture enabled, iOS deployment target 15.1+, and Android minSdkVersion 24+. Not checked yet
4 details in Everything
DataDome's Google Cloud Load Balancer module adds the DATADOME_USE_X_FORWARDED_HOST setting to read the request host from the X-Forwarded-Host header︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
DataDome's Google Cloud Load Balancer module adds DATADOME_USE_X_FORWARDED_HOST to pass the correct host when a proxy sits in front of the load balancer︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
When a reverse proxy or CDN CDN A content delivery network, servers distributed across locations that cache and serve content near readers. It can reduce loading time and traffic to the original server. sits in front of your Google Cloud Load Balancer and DataDome is seeing the wrong host, enable this setting so the module reads the correct host from the X-Forwarded-Host header.
env
copy
DATADOME_USE_X_FORWARDED_HOST=true
DataDome's Akamai integration adds JA3 JA3 A method for fingerprinting TLS clients by hashing fields from the ClientHello message, producing a short string that identifies the TLS library or application making a connection regardless of IP or port. and JA4 JA4 A network fingerprinting method that hashes observable TLS handshake fields into a short, readable tag, giving cyber tools a stable, version-agnostic way to classify clients and detect anomalies. TLS fingerprint collection in version 2.4.0︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Collect JA3 and JA4 TLS fingerprints in the Akamai integration to enrich bot detection signals sent to the Bot Protect API.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 more in Everything
DataDome's Akamai Edge Worker integration adds JA3 JA3 A method for fingerprinting TLS clients by hashing fields from the ClientHello message, producing a short string that identifies the TLS library or application making a connection regardless of IP or port. and JA4 JA4 A network fingerprinting method that hashes observable TLS handshake fields into a short, readable tag, giving cyber tools a stable, version-agnostic way to classify clients and detect anomalies. TLS fingerprinting support︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Configure Akamai to capture and forward TLS client hello data so DataDome can compute JA3/JA4 fingerprints for bot detection.
📍 In Akamai Property Manager, go to Property Variables and add:
Name: PMUSER_EW_TLS_CLIENT_HELLO
Initial Value: %(AK_CLIENT_HELLO)
Then ask your Akamai representative to add to ESSLINDEX Metadata Extensions under Deployment Settings:
<save-client-hello>on</save-client-hello>
Prerequisite: Certificate Provisioning System (CPS) must have Enhanced TLS configured for your domain.
Enable JA3/JA4 TLS fingerprinting on Akamai by adding <save-client-hello>on</save-client-hello> to ESSLINDEX Metadata Extensions under Deployment Settings, then defining the PMUSER_EW_TLS_CLIENT_HELLO Property Variable with initial value %(AK_CLIENT_HELLO) in Property Manager — requires Enhanced TLS configured in Certificate Provisioning System (CPS).︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 detail in Everything
JavaScript Tag 5.11.5 (2026-11-16)
Nov 16, 2026
·
issue 142
JavaScript Tag 5.11.3 (2026-11-09)
Nov 9, 2026
·
issue 135
Google Cloud Load Balancer module 1.9.0 (2026-11-09)
Nov 9, 2026
·
issue 135
DataDome's Google Cloud Load Balancer module adds DATADOME_USE_X_FORWARDED_HOST to read the request host from the X-Forwarded-Host header︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
When your Google Cloud Load Balancer sits behind a reverse proxy that sets X-Forwarded-Host, enable this setting so DataDome evaluates the correct original hostname rather than the proxy's host.
env
copy
DATADOME_USE_X_FORWARDED_HOST=true
React Native SDK for Fetch 3.0.0 (2026-11-03)
Nov 3, 2026
·
issue 130
DataDome React Native SDK for Fetch 3.0.0 rewrites on top of CoreDataDome SDK, replacing the singleton API with createDataDomeFetch(dataDome) and native challenge presentatio︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Initialize DataDome protection for all fetch calls in a React Native app using the new client-based API.
javascript
copy
import { DataDome } from '@datadome/react-native-core-datadome';
import { createDataDomeFetch } from '@datadome/react-native-datadome-fetch';
const dataDome = new DataDome({ clientKey: '<your-client-key>' });
const protectedFetch = createDataDomeFetch(dataDome);
// Use protectedFetch anywhere you would use fetch
const response = await protectedFetch('https://api.example.com/data');
Replace DataDomeFetch and the DataDome singleton (DataDome.configure, DataDome.getInstance) with createDataDomeFetch(dataDome) , which takes a DataDome client created with new DataDome({ clientKey }) and returns a fetch-compatible function that automatically adds DataDome headers to every request and checks every response for a challenge.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Accept a string, URL, or Request as fetch input, and a Headers object, an array of pairs, or a plain object as headers. Not checked yet Re-export DataDome, ResponseValidationStatus, DataDomeConfiguration, and DataDomeCookie from @datadome/react-native-core-datadome. Not checked yet Return the server response as-is when the CoreDataDome SDK fails, so a DataDome error never blocks the app's request. Not checked yet Rewrite the package in TypeScript. Not checked yet
Replace DataDomeFetch and the DataDome singleton (DataDome.configure, DataDome.getInstance) with createDataDomeFetch(dataDome) , which takes a DataDome client created with new DataDome({ clientKey }) and returns a fetch-compatible function that automatically adds DataDome headers to every request and checks every response for a challenge.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Re-export DataDome, ResponseValidationStatus, DataDomeConfiguration, and DataDomeCookie from @datadome/react-native-core-datadome. Not checked yet
3 more in Everything
└──▷ BREAKING ON UPGRADE
!
The package is renamed from `@datadome/react-native-datadome` to `@datadome/react-native-datadome-fetch`; update all imports and your package.json dependency.
Our best guess
!
`@datadome/react-native-core-datadome` is now a required peer dependency and must be installed alongside this package.
Our best guess
!
`DataDomeFetch`, `DataDome.configure`, and `DataDome.getInstance` are removed; replace them with createDataDomeFetch(new DataDome({ clientKey })).
Our best guess
!
The `datadome` per-request option is removed; the returned fetch function now applies DataDome headers and challenge checks to every request automatically.
Our best guess
!
`DataDomeModal`, `DataDomeModule`, and `enableVerboseLogs` are removed.
Our best guess
!
The `react-native-webview` peer dependency is removed; challenges are now presented natively by the CoreDataDome SDK.
Our best guess
!
React Native 0.85 or newer with the New Architecture is now required, along with iOS 15.1 or newer and Android API 24 or newer.
Our best guess
Node.js module 2.7.0 (2026-10-28)
Oct 28, 2026
·
issue 124
DataDome Node.js module 2.7.0 adds TLS fingerprint collection to enrich bot-detection signals︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
DataDome now collects TLS fingerprints from incoming requests to send richer bot-detection signals to the Bot Protect API.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet DataDome now includes the RequestMetadata property in the TypeScript type definitions. Not checked yet
DataDome now collects TLS fingerprints from incoming requests to send richer bot-detection signals to the Bot Protect API.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 more in Everything
Cloudflare Worker Rust module 1.0.0 (2026-10-27)
Oct 27, 2026
·
issue 123
Adds the datadome-cloudflare-worker Rust crate for native DataDome bot protection inside Cloudflare Workers.
Fraud SDK .Net 2.1.0 (2026-10-27)
Oct 27, 2026
·
issue 123
DataDome Fraud SDK .Net 2.1.0 adds optional eventDate field to set effective event time in payloads.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Pass eventDate in a fraud event payload to record the actual time an event occurred rather than the submission time — useful for replaying or backfilling events.
json
copy
{
"eventDate": "2026-10-27T14:32:00Z",
"...": "..."
}
DataDome adds full server-side and client-side bot-protection integration for the Azion edge platform︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Scope bot-protection to login and checkout paths only, exclude your admin area, and enable GraphQL extraction for your /graphql endpoint — all in the firewall function Arguments.
json
copy
{
"serverSideKey": "<your-server-side-key>",
"urlPatternInclusion": "/login|/checkout",
"urlPatternExclusion": "/admin/",
"enableGraphQLSupport": true,
"graphQLEndpoint": "/graphql"
}
Enable Model Context Protocol Model Context Protocol Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. support on a custom MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. endpoint and raise the body-read limit for large MCP payloads.
json
copy
{
"serverSideKey": "<your-server-side-key>",
"enableMCPSupport": true,
"mcpEndpoint": "/mcp,/mcp-v2",
"maximumBodySize": 51200
}
Inject the DataDome JS Tag via your own first-party domain and raise the response-body buffer limit to 4 MB for large HTML pages.
json
copy
{
"clientSideKey": "<your-client-side-key>",
"jsURL": "https://ddfoo.example.com/tags.js",
"originURL": "https://origin.example.com",
"maximumResponseBodySize": 4194304
}
Adds serverSideKey, endpoint, timeout, urlPatternExclusion, urlPatternInclusion, staticAssetExclusion, encodedCharInclusion, removeMatrixParams, ipExclusion, logEnrichedHeaders, enableDebugging, customFieldString1-3, customFieldInteger1-2, customFieldFloat1, userID, and productID server-side arguments to the firewall.js Azion firewall function for fine-grained bot-protection control.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds enableGraphQLSupport and graphQLEndpoint server-side arguments to extract GraphQL operation name and type on requests to a GraphQL endpoint, improving protection for GraphQL APIs. Not checked yet Adds enableMCPSupport and mcpEndpoint server-side arguments to enable Model Context Protocol support and extract MCP information at a configurable endpoint. Not checked yet Adds maximumBodySize server-side argument (default 25600 bytes / 25 KB) to cap the request body read for GraphQL and MCP extraction. Not checked yet Adds clientSideKey, jsURL, jsTagOptions, originURL, and maximumResponseBodySize client-side arguments to the js-tag-injection.js Azion application function for JS Tag injection into HTML responses. Not checked yet
+1 more
show less
Adds maximumResponseBodySize client-side argument (default 2 MB) to control the HTML response size threshold above which the JS Tag is skipped and the response is passed through unmodified. Not checked yet
6 details in Everything
Fastly Compute Rust module 1.0.0 (2026-10-21)
Oct 21, 2026
·
issue 116
Azion module 1.0.0 (2026-10-21)
Oct 21, 2026
·
issue 116
Fraud SDK Java 3.1.0 (2026-10-21)
Oct 21, 2026
·
issue 116
Fraud SDK Java 3.1.0 adds optional eventDate field to supply the effective event time.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Android SDK 3.1.0 (2026-10-21)
Oct 21, 2026
·
issue 115
DataDome Android SDK 3.1.0 adds predictive back support with configurable BackBehaviour on Android 13+.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
Opt in to Android predictive back so DataDome's BackBehaviour controls what happens when a user swipes back on a protected screen.
app/src/main/AndroidManifest.xml
copy
<application
android:enableOnBackInvokedCallback="true"
... />
Adds support for Android predictive back gesture via BackBehaviour enum (BLOCKED, GO_BACKGROUND, GO_BACK), honoured on Android 13+ when the app sets android:enableOnBackInvokedCallback="true" or targets API 36+.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Requires androidx.activity 1.6.1 and compileSdk 33 or higher. Not checked yet
Adds support for Android predictive back gesture via BackBehaviour enum (BLOCKED, GO_BACKGROUND, GO_BACK), honoured on Android 13+ when the app sets android:enableOnBackInvokedCallback="true" or targets API 36+.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 more in Everything
└──▷ BREAKING ON UPGRADE
! The SDK now requires androidx.activity 1.6.1 and apps must compile with compileSdk 33 or higher; projects on lower compile SDK versions will fail to build.
Fraud SDK Go v2.1.0 (2026-10-02)
Oct 2, 2026
·
issue 092
DataDome Fraud SDK Go v2.1.0 adds optional eventDate field for setting effective event time in payloads.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Flutter Dio SDK 3.5.0 (2026-10-02)
Oct 2, 2026
·
issue 092
DataDome Flutter Dio SDK 3.5.0 adds Swift Package Manager support for iOS and an iOS privacy manifest.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Adds Swift Package Manager (SPM) support for iOS native dependencies alongside existing CocoaPods support; apps on Flutter 3.44+ with SPM enabled resolve the plugin via SPM automatically.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds an iOS privacy manifest (PrivacyInfo.xcprivacy) to the plugin. Not checked yet
2 details in Everything
DataDome adds AI Key Takeaways to Homepage & Trend Reports, delivering real-time security and business summaries for Enterprise plans.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ HOW TO FIND IT
Switch from the security analyst view to the executive business view inside AI Key Takeaways to prepare a monthly risk report without rebuilding data from scratch.
📍 In the DataDome dashboard, go to Homepage or Trend Reports › AI Key Takeaways › toggle from Security view to Business view .
Adds AI Key Takeaways to the DataDome Homepage & Trend Reports, providing a real-time AI-generated summary of threat data including sophisticated bots, AI agents, and threat traffic ratio.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Introduces a security view as the default mode of AI Key Takeaways, surfacing detection precision, critical escalations, unusual behavioral patterns, attack pattern analysis, and configuration recommendations. Not checked yet Introduces a business view toggle within AI Key Takeaways that reframes the same underlying data for executive audiences, covering protection status, threats blocked, false positive rates, and actionable guidance for internal reporting. Not checked yet
3 details in Everything
Google Cloud Load Balancer module 1.8.0
Sep 30, 2026
· release notes
DataDome Google Cloud Load Balancer module 1.8.0 adds JA3 JA3 A method for fingerprinting TLS clients by hashing fields from the ClientHello message, producing a short string that identifies the TLS library or application making a connection regardless of IP or port. and JA4 JA4 A network fingerprinting method that hashes observable TLS handshake fields into a short, readable tag, giving cyber tools a stable, version-agnostic way to classify clients and detect anomalies. TLS fingerprint support.
JA3 and JA4 TLS fingerprints Not checked yet
1 detail in Everything
DataDome CloudFront Node.js v3 splits exclusion config into two env vars and adds URI inspection defaults.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ USE IT
After upgrading to v3, separate your custom URL exclusions from static-asset exclusions so each variable covers only its intended scope.
.env
copy
DATADOME_URI_REGEX_EXCLUSION="/health|/heartbeat"
DATADOME_STATIC_ASSET_EXCLUSION="\.(css|gif|ico|jpg|js|png|svg|woff2)$"
Disable matrix-param stripping if your application relies on semicolons in URLs being passed through unmodified.
.env
copy
DATADOME_REMOVE_MATRIX_PARAMS=false
Adds DATADOME_STATIC_ASSET_EXCLUSION environment variable to hold static-asset extension exclusions separately from custom URL exclusions, enabled by default with a standard list.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Splits DATADOME_URI_REGEX_EXCLUSION so it now holds only custom URL exclusions, removing static-asset extensions from its scope. Not checked yet Adds DATADOME_REMOVE_MATRIX_PARAMS setting (enabled by default) so DataDome strips matrix params (;) before regex evaluation, matching existing query-param (?) handling. Not checked yet Adds DATADOME_ENCODED_CHAR_INCLUSION setting (enabled by default) to inspect static-looking paths containing encoded characters %23, %25, %2f, %3b, or %3f. Not checked yet
Adds DATADOME_STATIC_ASSET_EXCLUSION environment variable to hold static-asset extension exclusions separately from custom URL exclusions, enabled by default with a standard list.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet Adds DATADOME_REMOVE_MATRIX_PARAMS setting (enabled by default) so DataDome strips matrix params (;) before regex evaluation, matching existing query-param (?) handling. Not checked yet Adds DATADOME_ENCODED_CHAR_INCLUSION setting (enabled by default) to inspect static-looking paths containing encoded characters %23, %25, %2f, %3b, or %3f. Not checked yet
1 more in Everything
└──▷ BREAKING ON UPGRADE
! DATADOME_URI_REGEX_EXCLUSION no longer covers static-asset extensions — any static-asset patterns previously placed there must be moved to the new DATADOME_STATIC_ASSET_EXCLUSION variable or they will no longer be excluded.
Varnish module 3.6.0 (2026-09-25)
Sep 25, 2026
·
issue 085
DataDome Varnish module 3.6.0 adds support for Varnish 8.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Fraud SDK .NET 2.0.0 adds custom events and a builder pattern over API generation.
Adds ValidateCustom and CollectCustom methods to support submitting custom event payloads Not checked yet Adds .NET 8.0 platform support Not checked yet Updates client setup to the Client.Builder(...) pattern for dependency injection Not checked yet
3 details in Everything
└──▷ BREAKING ON UPGRADE
! The useForwarded configuration option is removed along with its header parsing! Asynchronous validate and collect calls are no longer supported! Client setup replaces AddDataDome DI registration and DataDomeOptions with the Client.Builder(...) pattern
DataDome adds static asset exclusion support to skip processing of common file types like CSS, JS, and images.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Supports excluding static assets (e.g., .css, .js, .jpg, .png, .webp, .pdf, .woff2, and 40+ other extensions) from DataDome processing to reduce unnecessary inspection overhead.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 detail in Everything
DataDome: Adds the ability to exclude static assets (.avi, .avif, .bmp, .css, .eot, .flac, .flv, .gif, .gz, .ico, .jpeg, .jpg, .js, .json, .less, .map, .mka, .mkv, .mov, .mp3, .mp4, .mpeg, .mpg, .ogg, .ogm, .opus, .otf, .pdf, .png, .svg, .svgz, .swf, .tif, .tiff, .ttf, .wav, .webm, .webp, .woff, .woff2, .xml, .zip) from DataDome processing to reduce unnecessary bot-detection overhead on non-dynamic resources.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
api-docs-b6ca6b54f992
Sep 13, 2026
·
issue 073
DataDome: Supports excluding static assets (e.g., css, js, jpg, png, woff2, mp4, zip, and 40+ other extensions) from DataDome processing to reduce unnecessary inspection overhead.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
api-docs-9a79fd98bf10
Sep 12, 2026
·
issue 072
DataDome adds static asset exclusion to skip processing of CSS, JS, images, media, and other non-dynamic file types.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Supports excluding static assets (e.g., avi, css, js, jpg, png, svg, mp4, woff2, zip, and dozens more) from DataDome processing via an exclusion list.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 detail in Everything
api-docs-734ce93c032f
Sep 11, 2026
·
issue 071
DataDome: Adds the ability to exclude static assets (e.g., avi, css, js, jpg, png, svg, woff2, zip, and 40+ other extensions) from DataDome processing.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
api-docs-d864889da5bc
Sep 10, 2026
·
issue 070
DataDome adds static asset exclusion support, letting you skip CSS, JS, images, and other non-dynamic files from bot protection processing.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Supports excluding static asset file types (including avi, avif, bmp, css, eot, flac, flv, gif, gz, ico, jpeg, jpg, js, json, less, map, mka, mkv, mov, mp3, mp4, mpeg, mpg, ogg, ogm, opus, otf, pdf, png, svg, svgz, swf, tif, tiff, ttf, wav, webm, webp, woff, woff2, xml, zip) from DataDome processing to reduce unnecessary inspection of non-dynamic content.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Not checked yet
1 detail in Everything
DataDome CloudFront v3 splits exclusion config into two env vars and adds two new default URI checks
└──▷ USE IT
Separate your custom URL exclusions from static-asset exclusions so DataDome correctly applies both independently.
env
copy
DATADOME_URI_REGEX_EXCLUSION='/health|/heartbeat'
DATADOME_STATIC_ASSET_EXCLUSION=true
Enable encoded-character inspection to catch bots probing static-looking paths with encoded chars like %2f or %3f.
env
copy
DATADOME_ENCODED_CHAR_INCLUSION=true
DATADOME_REMOVE_MATRIX_PARAMS=true
Introduces DATADOME_STATIC_ASSET_EXCLUSION environment variable to hold static-asset extension exclusions separately from custom URL exclusions, enabled by default. Not checked yet Moves custom URL exclusions to DATADOME_URI_REGEX_EXCLUSION exclusively — static-asset extensions must now be removed from this variable. Not checked yet Adds DATADOME_REMOVE_MATRIX_PARAMS setting (enabled by default) so DataDome strips matrix params (;) from URIs before regex evaluation. Not checked yet Adds DATADOME_ENCODED_CHAR_INCLUSION setting (enabled by default) to inspect static-looking paths containing encoded characters %23, %25, %2f, %3b, or %3f. Not checked yet Migrates the DataDome CloudFront Node.js module from CommonJS (module.exports / require) to ES Module (export / import) format, requiring .js files to be renamed to .mjs. Not checked yet
+1 more
show less
Migrates the Lambda@Edge Lambda@Edge An AWS feature that runs Lambda functions at CloudFront edge locations, letting cyber tools execute logic closer to users without managing servers in each region. function handler from callback-based signature to async/await pattern, enabling compatibility with Node.js runtime version 24 and later. Not checked yet
Introduces DATADOME_STATIC_ASSET_EXCLUSION environment variable to hold static-asset extension exclusions separately from custom URL exclusions, enabled by default. Not checked yet Adds DATADOME_REMOVE_MATRIX_PARAMS setting (enabled by default) so DataDome strips matrix params (;) from URIs before regex evaluation. Not checked yet Adds DATADOME_ENCODED_CHAR_INCLUSION setting (enabled by default) to inspect static-looking paths containing encoded characters %23, %25, %2f, %3b, or %3f. Not checked yet
3 more in Everything
└──▷ BREAKING ON UPGRADE
! Static-asset extension patterns must be removed from DATADOME_URI_REGEX_EXCLUSION; leaving them there duplicates or conflicts with the new DATADOME_STATIC_ASSET_EXCLUSION variable.! CommonJS .js files in the Lambda@Edge function must be renamed to .mjs and updated to use export/import syntax instead of module.exports/require.! Callback-based Lambda@Edge handler signature (exports.handler = (event, context, callback) => {}) must be replaced with the async/await pattern (exports.handler = async (event, context) => {}).
Nginx Module 3.1.0 (2026-09-07)
Sep 7, 2026
·
issue 068
Nginx Module 3.1.0 adds tif, tiff, and pdf to static asset exclusion and adopts dynamic API-driven status codes.
Extends the static asset exclusion regex pattern to cover tif, tiff, and pdf file extensions, skipping DataDome checks for those requests. Not checked yet Replaces hard-coded HTTP status codes with values sourced from DataDome Protection API response headers, enabling dynamic status code handling for upcoming features. Not checked yet
2 more in Everything
DataDome CloudFront v3 splits URI exclusions and adds matrix-param and encoding checks by default
Adds DATADOME_STATIC_ASSET_EXCLUSION environment variable (new in v3) to hold static-asset extension exclusions separately, enabled by default with a standard extension list — previously these lived inside DATADOME_URI_REGEX_EXCLUSION. Not checked yet Adds DATADOME_REMOVE_MATRIX_PARAMS setting (enabled by default) so DataDome strips matrix params (;) from URIs before regex evaluation, matching existing query-param (?) handling. Not checked yet Adds DATADOME_ENCODED_CHAR_INCLUSION setting (enabled by default) so DataDome inspects static-looking paths that contain encoded characters %23, %25, %2f, %3b, or %3f. Not checked yet
3 details in Everything
└──▷ BREAKING ON UPGRADE
! Static-asset extension patterns must be removed from DATADOME_URI_REGEX_EXCLUSION and are now controlled via the new DATADOME_STATIC_ASSET_EXCLUSION variable; leaving them in DATADOME_URI_REGEX_EXCLUSION after upgrading to v3 duplicates or conflicts with the new default list.! DATADOME_REMOVE_MATRIX_PARAMS is enabled by default in v3, meaning matrix-param URIs that were previously passed through will now be stripped before regex evaluation — disable only if this breaks application compatibility.! DATADOME_ENCODED_CHAR_INCLUSION is enabled by default in v3, meaning paths containing %23 %25 %2f %3b %3f that previously appeared static will now be inspected — disable only if this breaks application compatibility.
└──▷ BREAKING ON UPGRADE
! DATADOME_URI_REGEX_EXCLUSION now holds only custom URL exclusions — static-asset extension exclusions that were previously part of this setting are moved to the new DATADOME_STATIC_ASSET_EXCLUSION setting. Any existing static-asset patterns in DATADOME_URI_REGEX_EXCLUSION must be migrated to DATADOME_STATIC_ASSET_EXCLUSION to remain effective.
DataDome: Adds DATADOME_STATIC_ASSET_EXCLUSION environment variable to hold static-asset extension exclusions separately from custom URL exclusions, enabled by default with a standard list of extensions.
Narrows DATADOME_URI_REGEX_EXCLUSION to hold only custom URL exclusions (e.g. /health|/heartbeat), no longer bundling static-asset extensions. Not checked yet
1 detail in Everything
└──▷ BREAKING ON UPGRADE
! In v3, static-asset extension exclusions must move out of DATADOME_URI_REGEX_EXCLUSION and into the new DATADOME_STATIC_ASSET_EXCLUSION variable; leaving them in DATADOME_URI_REGEX_EXCLUSION duplicates or conflicts with the new default list.
DataDome CloudFront module 3.0.0 splits exclusion config and adds encoded-path inspection via three new settings
Adds DATADOME_ENCODED_CHAR_INCLUSION setting (enabled by default) to force inspection of static-looking paths that carry an encoded delimiter, with a configurable delimiter list (defaults: %23 %25 %2f %3b %3f). Not checked yet
1 detail in Everything
└──▷ BREAKING ON UPGRADE
! DATADOME_URI_REGEX_EXCLUSION no longer contains static-asset extension exclusions — those are moved to the new DATADOME_STATIC_ASSET_EXCLUSION setting. Any custom regex rules previously sharing that list must be re-verified to ensure static-asset entries were not relied upon there.! DATADOME_STATIC_ASSET_EXCLUSION is enabled by default in 3.0.0, changing exclusion evaluation behaviour for static assets on upgrade.! DATADOME_REMOVE_MATRIX_PARAMS is enabled by default in 3.0.0, changing how URLs with matrix parameters are matched against exclusion patterns on upgrade.! DATADOME_ENCODED_CHAR_INCLUSION is enabled by default in 3.0.0, causing paths with encoded delimiters (%23 %25 %2f %3b %3f) that previously passed through as excluded static assets to now be sent for bot inspection on upgrade.
DataDome CloudFront v3 splits exclusion config and adds default URI inspection for matrix params and encoded chars
└──▷ USE IT
Migrate a v2 combined exclusion variable to the v3 split config, keeping only custom health-check paths in DATADOME_URI_REGEX_EXCLUSION and relying on DATADOME_STATIC_ASSET_EXCLUSION for static assets.
env
copy
DATADOME_URI_REGEX_EXCLUSION="/health|/heartbeat"
DATADOME_STATIC_ASSET_EXCLUSION="\.(avi|avif|bmp|css|eot|flac|flv|gif|gz|ico|jpeg|jpg|js|json|less|map|mka|mkv|mov|mp3|mp4|mpeg|mpg|ogg|ogm|opus|otf|png|svg|svgz|swf|ttf|wav|webm|webp|woff|woff2|xml|zip)$"
Adds DATADOME_STATIC_ASSET_EXCLUSION environment variable to hold static-asset extension exclusions (standard list, enabled by default), separating them from custom URL exclusions previously combined in DATADOME_URI_REGEX_EXCLUSION. Not checked yet DATADOME_URI_REGEX_EXCLUSION now holds only custom URL exclusions — static-asset extensions must be moved out of this variable when upgrading to v3. Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
! DATADOME_URI_REGEX_EXCLUSION no longer holds static-asset extensions by default in v3 — any extension patterns (e.g. \.(css|js|png|…)$) must be removed from this variable and left to the new DATADOME_STATIC_ASSET_EXCLUSION variable, or existing exclusions will be double-listed or lost.
DataDome CloudFront integration 3.0.0 restructures exclusion and URL-evaluation settings with three new dedicated config keys.
Adds DATADOME_STATIC_ASSET_EXCLUSION setting (enabled by default) to hold static-asset file-extension exclusions in a dedicated list, separating them from custom URL exclusions previously mixed into DATADOME_URI_REGEX_EXCLUSION. Not checked yet Adds DATADOME_REMOVE_MATRIX_PARAMS setting (enabled by default) to strip RFC 3986 matrix parameters from URLs before evaluating exclusion patterns. Not checked yet
2 details in Everything
└──▷ BREAKING ON UPGRADE
! DATADOME_URI_REGEX_EXCLUSION now holds only custom URL exclusions; static-asset extensions it previously covered are moved to the new DATADOME_STATIC_ASSET_EXCLUSION setting — any custom static-asset patterns left in DATADOME_URI_REGEX_EXCLUSION must be migrated.! DATADOME_REMOVE_MATRIX_PARAMS is enabled by default, meaning matrix parameters are silently stripped from URLs during exclusion-pattern evaluation on upgrade — configurations that relied on matching matrix parameters will no longer match.! DATADOME_ENCODED_CHAR_INCLUSION is enabled by default, meaning paths with encoded delimiters (%23 %25 %2f %3b %3f) that were previously skipped as static assets will now be sent to DataDome for inspection on upgrade.
DataDome v3 splits URL exclusion config and adds matrix-param and encoding checks by default
Adds DATADOME_STATIC_ASSET_EXCLUSION environment variable to hold static-asset extension exclusions separately, enabled by default with a standard list — freeing DATADOME_URL_REGEX_EXCLUSION for application-specific URL exclusions only. Not checked yet Adds DATADOME_REMOVE_MATRIX_PARAMS setting (enabled by default) so matrix parameters (;) are stripped before regex evaluation, matching existing query-parameter behaviour. Not checked yet Adds DATADOME_ENCODED_CHAR_INCLUSION setting (enabled by default) to inspect static-looking paths that contain any of %23, %25, %2f, %3b, or %3f. Not checked yet
3 details in Everything
└──▷ BREAKING ON UPGRADE
! In v2, DATADOME_URL_REGEX_EXCLUSION also excluded static-asset extensions; in v3 those extensions move to the new DATADOME_STATIC_ASSET_EXCLUSION variable — any static-asset patterns left in DATADOME_URL_REGEX_EXCLUSION must be removed to avoid duplication or misconfiguration.
api-docs-c11305f974b4
Aug 28, 2026
·
issue 058
DataDome API adds AcceptLanguage, Via, SecCHUAFullVersionList, and three CustomFieldString fields to its reference.
Adds AcceptLanguage field to the DataDome API reference for passing the request's Accept-Language header to the detection engine. Not checked yet Adds Via field to the DataDome API reference for forwarding proxy chain information. Not checked yet Adds SecCHUAFullVersionList field to the DataDome API reference for passing the Sec-CH-UA-Full-Version-List client hint header. Not checked yet Adds CustomFieldString1, CustomFieldString2, and CustomFieldString3 fields to the DataDome API reference for sending arbitrary custom string data alongside detection requests. Not checked yet
4 details in Everything
DataDome launches a hosted MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server giving AI agents direct natural-language access to Trend Reports data.
└──▷ HOW TO FIND IT
Connect an MCP-compatible AI agent to DataDome's hosted MCP endpoint to query Trend Reports in natural language from within existing workflows.
📍 In your MCP-compatible AI agent or tool, configure the server connection to DataDome's hosted MCP endpoint and authenticate using your existing DataDome credentials.
New hosted MCP server exposes DataDome Trend Reports data to MCP-compatible AI agents and agentic workflows, authenticated via existing DataDome credentials — no custom integration or infrastructure required. Not checked yet Enables AI agents to query automated traffic trends, threat types, scraping activity, and credential-stuffing patterns in natural language directly from tools like Slack-connected assistants, enterprise copilots, or custom agent pipelines. Not checked yet
2 details in Everything
DataDome Cloudflare Worker 3.0.0 splits URL exclusion config and enables matrix-param/encoding checks by default
└──▷ USE IT
Migrate to v3.0.0 by splitting your exclusion config: keep only custom health-check paths in DATADOME_URL_REGEX_EXCLUSION and let DATADOME_STATIC_ASSET_EXCLUSION handle static assets automatically.
.env
copy
DATADOME_URL_REGEX_EXCLUSION="/health|/heartbeat"
DATADOME_STATIC_ASSET_EXCLUSION=".(avi|avif|bmp|css|eot|flac|gif|gz|ico|jpeg|jpg|js|json|mp3|mp4|ogg|otf|png|svg|ttf|wav|webm|webp|woff|woff2|xml|zip)$"
Adds DATADOME_STATIC_ASSET_EXCLUSION env var to hold static-asset file-extension exclusions separately from custom URL patterns, enabled by default with a standard extension list. Not checked yet DATADOME_URL_REGEX_EXCLUSION now holds only custom URL exclusions (e.g. /health|/heartbeat); static-asset extensions must be migrated out of it. Not checked yet Adds DATADOME_REMOVE_MATRIX_PARAMS setting to strip matrix params (;) before regex evaluation, mirroring existing query-param (?) handling, enabled by default. Not checked yet Adds DATADOME_ENCODED_CHAR_INCLUSION setting to inspect static-looking paths that contain encoded characters %23, %25, %2f, %3b, or %3f, enabled by default. Not checked yet
4 details in Everything
└──▷ BREAKING ON UPGRADE
! In v3.0.0, static-asset file extensions must be moved out of DATADOME_URL_REGEX_EXCLUSION into the new DATADOME_STATIC_ASSET_EXCLUSION variable; any extensions left in DATADOME_URL_REGEX_EXCLUSION will be treated as custom URL exclusions rather than static-asset exclusions.! DATADOME_REMOVE_MATRIX_PARAMS and DATADOME_ENCODED_CHAR_INCLUSION are enabled by default in v3.0.0; applications that require the old behaviour must explicitly disable them.
└──▷ USE IT
Migrate a v2 config to v3 by splitting static-asset extensions out of your custom URL exclusions into the dedicated variable.
.env
copy
# .env / Cloudflare Worker environment variables
DATADOME_URL_REGEX_EXCLUSION="/health|/heartbeat"
DATADOME_STATIC_ASSET_EXCLUSION="\.(avi|avif|bmp|css|eot|flac|gif|gz|ico|jpeg|jpg|js|json|less|map|mp3|mp4|png|svg|ttf|woff|woff2|xml|zip)$"
Narrows DATADOME_URL_REGEX_EXCLUSION to hold only custom URL exclusions — static-asset extensions must now be moved to the new DATADOME_STATIC_ASSET_EXCLUSION variable. Not checked yet Enables matrix-parameter stripping via DATADOME_REMOVE_MATRIX_PARAMS by default, ignoring semicolon-delimited params (;) before regex evaluation, matching existing query-param (?) behaviour. Not checked yet Enables encoded-character inspection via DATADOME_ENCODED_CHAR_INCLUSION by default, causing DataDome to inspect static-looking paths that contain %23, %25, %2f, %3b, or %3f. Not checked yet
└──▷ BREAKING ON UPGRADE
! Any static-asset extensions previously listed in DATADOME_URL_REGEX_EXCLUSION (e.g. .css, .js, .png, etc.) must be moved to the new DATADOME_STATIC_ASSET_EXCLUSION variable; leaving them in DATADOME_URL_REGEX_EXCLUSION will cause them to be evaluated as bot-detection candidates rather than excluded.! DATADOME_REMOVE_MATRIX_PARAMS is now on by default — deployments that rely on matrix params being passed through unchanged must explicitly disable this setting.! DATADOME_ENCODED_CHAR_INCLUSION is now on by default — paths containing %23, %25, %2f, %3b, or %3f that were previously excluded as static assets will now be inspected; disable the setting only if it causes compatibility issues.
DataDome Cloudflare module 3.0.0 adds three new config settings for static-asset exclusion, matrix-param handling, and encoded-char inspection.
└──▷ USE IT
Keep custom URL exclusions separate from static-asset exclusions now that the two settings are split in 3.0.0.
ini
copy
DATADOME_STATIC_ASSET_EXCLUSION = true
DATADOME_URL_REGEX_EXCLUSION = "^/api/internal/.*"
Adds DATADOME_STATIC_ASSET_EXCLUSION setting (enabled by default) that moves static-asset file-extension exclusions into a dedicated list, so DATADOME_URL_REGEX_EXCLUSION now holds only custom URL exclusions. Not checked yet Adds DATADOME_REMOVE_MATRIX_PARAMS setting (enabled by default) to strip RFC 3986 matrix parameters from URLs before matching against exclusion patterns. Not checked yet Adds DATADOME_ENCODED_CHAR_INCLUSION setting (enabled by default) to force inspection of static-looking paths that carry an encoded delimiter — defaults to %23, %25, %2f, %3b, %3f, with custom values supported. Not checked yet Removes hard-coded HTTP status codes in favor of DataDome Protection API response headers, enabling forward-compatible support for new API features. Not checked yet
4 details in Everything
└──▷ BREAKING ON UPGRADE
! The DATADOME_URL_REGEX_EXCLUSION setting no longer includes static-asset extension patterns — those are now managed by the new DATADOME_STATIC_ASSET_EXCLUSION setting. Any custom regexes that were duplicating built-in static-asset exclusions should be reviewed to avoid redundancy or gaps.
DataDome CloudFront integration now supports the nodejs26.x Lambda runtime.
Tyk module 1.4.0 (2026-08-24)
Aug 24, 2026
·
issue 055
DataDome Tyk module 1.4.0 adds GraphQL path detection and X-Forwarded-Host support.
└──▷ USE IT
Route GraphQL traffic detection across multiple non-standard endpoints in a Tyk plugin config.
ini
copy
datadome_graphql_endpoint = graphql,api/graphql,query
Enable host override via the X-Forwarded-Host header when DataDome sits behind a reverse proxy that rewrites the Host.
ini
copy
datadome_use_x_forwarded_host = true
Adds datadome_graphql_endpoint config option to define one or more paths (comma-separated) used to detect GraphQL requests, defaulting to graphql. Not checked yet Adds datadome_use_x_forwarded_host config option to support host override via the X-Forwarded-Host header. Not checked yet Adds support for 301/302 redirects. Not checked yet
3 details in Everything
DataDome Envoy module 2.8.0 adds GraphQL support with configurable endpoint extraction.
Adds ENABLE_GRAPHQL_SUPPORT setting (set to true) to enable GraphQL request handling in the Envoy module starting with v2.8.0. Not checked yet Adds GRAPHQL_ENDPOINT setting (default: /graphql) to specify one or more comma-separated endpoints from which the GraphQL operation name and type are extracted. Not checked yet
2 details in Everything
Envoy module 2.8.0 (2026-08-21)
Aug 21, 2026
·
issue 053
DataDome Envoy module 2.8.0 adds GraphQL support.
iOS SDK for Alamofire 4.1.0 (2026-08-20)
Aug 20, 2026
·
issue 051
DataDome iOS Alamofire SDK 4.1.0 automatically merges DataDome cookies with manually added request cookies.
Magento module 1.2.247 (2026-08-19)
Aug 19, 2026
·
issue 050
Magento module 1.2.247 adds the datadome_enable_mcp_support property.
DataDome Cloudflare Worker Terraform module v2.7.0 adds DATADOME_GRAPHQL_ENDPOINT and DATADOME_MCP_ENDPOINT configuration settings.
Adds DATADOME_GRAPHQL_ENDPOINT config setting (module v2.7.0+) to specify one or more GraphQL endpoints (comma-separated) from which the operation name and type are extracted for analysis. Not checked yet Adds DATADOME_MCP_ENDPOINT config setting (module v2.7.0+) to specify one or more MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. endpoints (comma-separated) so that requests targeting those endpoints are analyzed to extract MCP properties. Not checked yet
2 details in Everything
DataDome Cloudflare Worker v2.7.0 adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. endpoint analysis, GraphQL endpoint config, and enriched headers access.
└──▷ USE IT
Access enriched DataDome headers in your Cloudflare Worker to log or forward request classification metadata downstream.
typescript
copy
async fetch(
request: Request,
env: Env,
ctx: ExecutionContext,
): Promise<Response> {
const response = await dataDomeHandler.fetch(request as any, env, ctx);
console.log(
Object.entries(ctx.dataDomeEnrichedHeaders)
.map(([name, value]) => `${name}: ${value}`)
.join(' - '),
);
return response;
}
Adds graphQLEndpoint config setting to customize which endpoints have GraphQL operation name and type extracted; accepts multiple endpoints as a comma-separated list. Not checked yet Adds mcpEndpoint config setting to designate MCP endpoints for automated MCP-property extraction; accepts multiple endpoints as a comma-separated list. Not checked yet Exposes enriched headers in ctx.dataDomeEnrichedHeaders after calling dataDomeHandler.fetch() , making DataDome's request metadata available for downstream Cloudflare Worker logic. Not checked yet
3 details in Everything
DataDome Cloudflare Worker adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. endpoint inspection and configurable GraphQL/MCP endpoint settings in v2.7.0
Adds DATADOME_MCP_ENDPOINT config setting (v2.7.0) to designate one or more MCP endpoints (comma-separated) for MCP property extraction and analysis. Not checked yet Adds DATADOME_GRAPHQL_ENDPOINT config setting (v2.7.0) to customize one or more GraphQL endpoints (comma-separated) from which operation name and type are extracted. Not checked yet
2 details in Everything
DataDome Cloudflare Worker adds DATADOME_GRAPHQL_ENDPOINT and DATADOME_MCP_ENDPOINT settings for targeted request analysis.
Adds DATADOME_GRAPHQL_ENDPOINT config setting to specify one or more GraphQL endpoints (comma-separated) from which operation name and type are extracted for analysis. Not checked yet Adds DATADOME_MCP_ENDPOINT config setting to specify one or more MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. endpoints (comma-separated) so that requests targeting them are analyzed to extract MCP properties. Not checked yet
2 details in Everything
DataDome Cloudflare integration 2.7.0 adds enriched headers for log enhancement and new DATADOME_GRAPHQL_ENDPOINT and DATADOME_MCP_ENDPOINT config parameters.
Adds DATADOME_GRAPHQL_ENDPOINT environment parameter to specify the GraphQL endpoint (defaults to /graphql). Not checked yet Adds DATADOME_MCP_ENDPOINT environment parameter to specify the MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. endpoint (defaults to /mcp). Not checked yet Adds enriched headers in context to enable log enhancement across all requests. Not checked yet
3 details in Everything
Apache module 3.0.0 splits URL exclusion config and adds three new directive defaults for static-asset and encoded-path handling.
Adds DomeStaticAssetExclusion directive (enabled by default) to handle static-asset extension exclusions, now including avif, gz, json, xml, and zip in the standard list. Not checked yet Adds DomeRemoveMatrixParams directive (enabled by default) to ignore matrix parameters during DataDome URL regex evaluation per RFC 3986. Not checked yet Adds DomeEncodedCharInclusion directive (enabled by default) to inspect static-looking paths carrying encoded delimiters %23, %25, %2f, %3b, and %3f. Not checked yet
3 details in Everything
└──▷ BREAKING ON UPGRADE
! DomeURIRegexExclusion now holds only custom URL exclusions; static-asset extension exclusions previously in DomeURIRegexExclusion move to the new DomeStaticAssetExclusion directive — any custom static-asset rules in DomeURIRegexExclusion must be migrated.
DataDome Apache module 3.0 splits URL exclusion settings and adds matrix-param and encoded-char inspection by default.
└──▷ USE IT
Migrate a 2.x Apache config to 3.0 by separating custom URL exclusions from static-asset extensions across the two new directives.
/etc/apache2/datadome.conf
copy
# Before (2.x)
DomeURIRegexExclusion="/health|/heartbeat|\.(css|js|png|gif|jpg)$"
# After (3.0)
DomeURIRegexExclusion="/health|/heartbeat"
DomeStaticAssetExclusion="\.(css|js|png|gif|jpg)$"
Adds DomeStaticAssetExclusion config directive to hold static-asset extension exclusions separately from DomeURIRegexExclusion, which now holds only custom URL exclusions. Not checked yet Adds DomeRemoveMatrixParams directive (default: On ) to strip matrix parameters (;...) per path segment before the exclusion regex is evaluated. Not checked yet Adds DomeEncodedCharInclusion directive to force inspection of static-looking paths containing encoded characters such as %23, %25, %2f, %3b, or %3f (default: "%23|%25|%2f|%3b|%3f"). Not checked yet
3 details in Everything
└──▷ BREAKING ON UPGRADE
! In 3.0.0, static-asset extension patterns must be moved out of DomeURIRegexExclusion into the new DomeStaticAssetExclusion directive; leaving them in DomeURIRegexExclusion duplicates or conflicts with the new default list.! DomeRemoveMatrixParams is enabled (On ) by default in 3.0.0, meaning matrix parameters are stripped before exclusion regex matching — setups relying on matrix params being passed through unchanged may behave differently.! DomeEncodedCharInclusion is enabled by default in 3.0.0, causing static-looking paths containing %23, %25, %2f, %3b, or %3f to be inspected rather than excluded.! The DebugMode parameter is deprecated since version 2.26 and replaced by a new directive used as 'API request timeout for both new and reused connections in ms'.
OpenResty module 1.7.0 (2026-08-18)
Aug 18, 2026
·
issue 049
DataDome OpenResty module 1.7.0 adds GraphQL endpoint and body-size config parameters
Adds datadome_graphql_endpoint configuration parameter to specify the GraphQL endpoint (defaults to graphql). Not checked yet Adds datadome_graphql_max_body_size configuration parameter to limit the request body size parsed for GraphQL requests. Not checked yet
2 details in Everything
Node.js module 2.6.0 (2026-08-17)
Aug 17, 2026
·
issue 049
DataDome Node.js module 2.6.0 adds a graphQLEndpoint parameter to designate GraphQL paths for bot protection.
└──▷ USE IT
Override the default GraphQL path when your API mounts GraphQL at a non-standard route.
json
copy
{
graphQLEndpoint: '/api/graphql'
}
Adds graphQLEndpoint parameter to specify the path(s) for the GraphQL endpoint, defaulting to /graphql. Not checked yet Adds validation of the logger parameter to ensure it contains every required method with the correct signature. Not checked yet
2 details in Everything
Cloudflare Worker module 2.7.0 (2026-08-17)
Aug 17, 2026
·
issue 049
DataDome Cloudflare Worker 2.7.0 adds enriched request headers and configurable GraphQL/MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. endpoint parameters.
└──▷ USE IT
Override the default GraphQL and MCP endpoints when your app exposes them at non-standard paths.
env
copy
DATADOME_GRAPHQL_ENDPOINT=/api/graphql
DATADOME_MCP_ENDPOINT=/api/mcp
Adds DATADOME_GRAPHQL_ENDPOINT parameter to specify the GraphQL endpoint (defaults to /graphql). Not checked yet Adds DATADOME_MCP_ENDPOINT parameter to specify the MCP endpoint (defaults to /mcp). Not checked yet Adds enriched headers in context to enable log enhancement across all requests. Not checked yet
3 details in Everything
Go module v2.5.0 (2026-07-28)
Jul 28, 2026
·
issue 028
DataDome Go module v2.5.0 adds a GraphQLEndpoint parameter to configure GraphQL path protection.
└──▷ USE IT
Override the default GraphQL path when your API exposes GraphQL at a non-standard route.
go
copy
GraphQLEndpoint: "/api/graphql"
Adds GraphQLEndpoint parameter to specify custom GraphQL endpoint paths (defaults to /graphql). Not checked yet
1 detail in Everything
Google Cloud Load Balancer module 1.7.0 (2026-07-28)
Jul 28, 2026
·
issue 028
DataDome's Google Cloud Load Balancer module adds configurable GraphQL endpoint path support.
└──▷ USE IT
Override the default GraphQL endpoint path when your API exposes GraphQL at a non-standard route.
yaml
copy
GraphQLEndpoint: /api/graphql
Adds GraphQLEndpoint parameter to specify custom paths for the GraphQL endpoint (defaults to /graphql). Not checked yet
1 detail in Everything
Python ASGI module 1.2.0 (2026-07-28)
Jul 28, 2026
·
issue 028
DataDome Python ASGI ASGI A Python async web server interface specification that defines how servers and applications exchange HTTP and WebSocket messages; cyber tools use it to serve high-concurrency APIs without blocking on I/O. module 1.2.0 adds configurable MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. endpoint support and expands cookie length to 512 chars.
Adds mcp_endpoint attribute to DataDomeMiddleware to specify a custom MCP endpoint path (defaults to /mcp). Not checked yet Increases DataDome cookie length limit from 128 to 512 characters to support future capabilities. Not checked yet
2 details in Everything
DataDome Envoy module now supports logging enriched Protection API headers via Envoy dynamic metadata.
DataDome adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. -aware payload fields and Session-by-Header (X-DataDome-ClientID) support to its Validate Request API.
└──▷ USE IT
Use Session by Header to track non-browser API clients that supply their own session ID instead of a cookie.
lua
copy
if request_headers['x-datadome-clientid'] ~= nil then
body['ClientID'] = request_headers['x-datadome-clientid']
datadomeHeaders["X-DataDome-X-Set-Cookie"] = "true"
else
body['ClientID'] = clientId
end
Supports Session by Header: integrations can now supply the client ID via the X-DataDome-ClientID request header as a higher-priority alternative to the datadome cookie, enabling session tracking for non-browser clients. Not checked yet Adds X-DataDome-X-Set-Cookie: true signaling so integrations using header-based client IDs receive the updated session value in X-Set-Cookie instead of Set-Cookie . Not checked yet Introduces Enriched Headers: the X-DataDome-request-headers pointer header lets integrations selectively inject upstream bot-signal headers (e.g., X-DataDome-isbot, X-DataDome-botname) into requests reaching the origin server. Not checked yet Adds MCP-specific payload fields (McpMethod, McpParamsClientInfoName, McpParamsClientInfoVersion, McpParamsToolName, McpProtocolVersion, McpSessionId) to the Protection API request schema. Not checked yet
4 details in Everything
Envoy module 2.7.0 (2026-07-21)
Jul 21, 2026
·
issue 021
DataDome Envoy module 2.7.0 exposes enriched headers as Envoy dynamic metadata for downstream logging.
Fastly Compute module 1.4.0 (2026-07-20)
Jul 20, 2026
·
issue 020
DataDome Fastly Compute 1.4.0 adds MCP MCP Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. protocol support with HTTP message signature collection per RFC 9421 RFC 9421 An IETF standard defining HTTP Message Signatures, a scheme for cryptographically signing HTTP requests and responses so tools can verify message integrity and authenticity end-to-end. .
└──▷ USE IT
Enable MCP traffic inspection by pointing DataDome at your MCP endpoint in the Fastly Compute service config.
ini
copy
datadome_mcp_endpoint = "/mcp"
Adds Model Context Protocol Model Context Protocol Model Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. (MCP) support with new datadome_mcp_endpoint configuration parameter (defaults to /mcp) to specify the MCP endpoint. Not checked yet Collects Signature , Signature-Agent , and Signature-Input headers to support HTTP message signatures as defined by RFC 9421. Not checked yet Collects Skyfire-Pay-ID header from incoming requests. Not checked yet
3 details in Everything
JavaScript Tag 5.9.0 (2026-07-20)
Jul 20, 2026
·
issue 020
DataDome JS Tag 5.9.0 adds challengeType to event payloads and the displayDataDomeResponsePage function for style adaptation.
Adds challengeType parameter to event payloads, exposing the type of challenge triggered in downstream event handling. Not checked yet Accepts challengeType in the displayDataDomeResponsePage function, enabling style adaptation based on the challenge type being displayed. Not checked yet
2 details in Everything
DataDome Terraform provider v2.4.0 (2026-06-30)
Jun 30, 2026
·
issue 014
DataDome Terraform provider v2.4.0 adds rate limiting, time-box policies, agentic endpoint types, and new response actions for custom rules.
└──▷ USE IT
Protect an agentic login endpoint with a rate-limit policy to throttle automated credential-stuffing agents.
hcl
copy
resource "datadome_custom_rule" "agentic_login_rate_limit" {
name = "Rate-limit agentic login"
endpoint_type = "agentic-login"
response = "intent_based"
policy = "rate_limit"
}
Apply a time-box policy with a device_check response to block suspicious agentic cart activity within a rolling window.
hcl
copy
resource "datadome_custom_rule" "agentic_cart_timebox" {
name = "Time-box agentic cart abuse"
endpoint_type = "agentic-cart"
response = "device_check"
policy = "time_box"
}
Adds rate_limit and time_box policy options for custom rules, enabling threshold-based and time-windowed enforcement. Not checked yet Adds six new endpoint_type values for custom rules targeting agentic AI traffic: agentic-general, agentic-account-creation, agentic-login, agentic-cart, agentic-forms, and agentic-payment. Not checked yet Adds three new response values for custom rules: device_check, intent_based, and monetize, expanding the range of enforcement actions available. Not checked yet
3 details in Everything
iOS SDK for Apollo 4.0.0 (2026-06-30)
Jun 30, 2026
·
issue 014
DataDome iOS SDK for Apollo 4.0.0 adds support for Apollo v2.
Supports Apollo v2 GraphQL client for iOS, enabling DataDome bot protection on Apollo v2-based apps. Not checked yet
1 detail in Everything