Retrieves a traffic time series data over a set of domains. The response is suitable for plotting a time series chart. This method allows filtering the traffic data by various criteria.
API key for authentication. Make sure to include the word apikey, followed by a single space and then your token.
Example: apikey 1234$abcdef
List of domain IDs. Empty list means all domains belonging to the current account.
Domain ID
[1, 2, 3]Specifies the granularity of the result data.
daily, hourly, minutely Filter data items starting from a specified date in ISO 8601 format
"2024-04-13T00:00:00+01:00"
Filter data items up to a specified end date in ISO 8601 format. If not provided, defaults to the current date and time.
"2024-04-14T12:00:00Z"
Filter traffic data by client IP.
["1.2.3.4", " 2001:678:194::3c25:ddad"]Filter by URL path with a glob-like pattern.
"/home"
Filter data by a country code of the originating IP address in ISO 3166-1 alpha-2 format.
["DE", "MY"]Filter data by HTTP response status code.
100 <= x <= 599["403", "499"]Filter by HTTP methods
An HTTP method of a request.
DELETE, GET, HEAD, OPTIONS, PATCH, POST, PUT, TRACE ["GET", "HEAD"]Filter data by reference IDs.
Filter data by request IDs.
Filter data by session IDs.
Filter data by name of a security rule matched the request.
100["SQL injection"]Filter data by decision.
Filter data by the event decision.
blocked, monitored, allowed, passed ["allowed", "blocked"]Filter data by optional action.
Filter data by the optional action.
captcha, challenge ["captcha", "challenge"]Successful Response
UNIX timestamp indicating when the traffic data was recorded
Traffic (number of requests) that was passed to the origin and didn't trigger any rules
Traffic blocked by a security policy, custom rule, or DDoS protection
Traffic that was identified as malicious by security policies (for monitored domains)
Traffic passed due to a permissive security rule