Skip to main content
GET
/
waap
/
v1
/
analytics
/
requests
Get request log data
curl --request GET \
  --url https://api.gcore.com/waap/v1/analytics/requests \
  --header 'Authorization: <api-key>'
{
  "limit": 123,
  "offset": 123,
  "count": 123,
  "results": [
    {
      "id": "<string>",
      "path": "<string>",
      "client_ip": "<string>",
      "method": "<string>",
      "rule_name": "<string>",
      "country": "<string>",
      "action": "<string>",
      "rule_id": "<string>",
      "domain": "<string>",
      "user_agent": "<string>",
      "user_agent_client": "<string>",
      "organization": "<string>",
      "request_time": 123,
      "reference_id": "<string>",
      "status_code": 123,
      "result": "passed",
      "traffic_types": "<string>"
    }
  ]
}

Authorizations

​
Authorization
string
header
required

API key for authentication. Make sure to include the word apikey, followed by a single space and then your token. Example: apikey 1234$abcdef

Query Parameters

​
domains
integer[]

List of domain IDs.

Domain ID

Example:
[1, 2, 3]
​
ordering
string

Sort data by given field.

Examples:

"userAgent"

"-requestTime"

​
start
string
required

Filter data items starting from a specified date in ISO 8601 format

Example:

"2024-04-13T00:00:00+01:00"

​
end
string | null

Filter data items up to a specified end date in ISO 8601 format. If not provided, defaults to the current date and time.

Example:

"2024-04-14T12:00:00Z"

​
limit
integer
default:100

Number of items to return

Required range: 0 <= x <= 100
​
offset
integer
default:0

Number of items to skip

Required range: 0 <= x <= 100000
​
traffic_types
enum<string>[]

Filter data by traffic types. A single request can be categorized into multiple traffic types.

A type of traffic that a request is categorized as.

Available options:
policy_allowed,
policy_blocked,
custom_rule_allowed,
custom_blocked,
legit_requests,
sanctioned,
dynamic,
api,
static,
ajax,
redirects,
monitor,
err_40x,
err_50x,
passed_to_origin,
timeout,
other,
ddos,
legit,
monitored
Example:
["policy_allowed", "custom_rule_allowed"]
​
ips
string<ipvanyaddress>[]

Filter traffic data by client IP.

Example:
["1.2.3.4", " 2001:678:194::3c25:ddad"]
​
actions
enum<string>[]

Filter data by security actions applied to the request.

An action applied to a request according to the security configuration.

Available options:
allow,
block,
captcha,
handshake
Example:
["captcha", "handshake"]
​
path
string | null

Filter by URL path with a glob-like pattern.

Example:

"/home"

​
countries
string[]

Filter data by a country code of the originating IP address in ISO 3166-1 alpha-2 format.

Example:
["DE", "MY"]
​
status_codes
integer[]

Filter data by HTTP response status code.

Required range: 100 <= x <= 599
​
http_methods
enum<string>[]

Filter by HTTP methods

An HTTP method of a request.

Available options:
DELETE,
GET,
HEAD,
OPTIONS,
PATCH,
POST,
PUT,
TRACE
Example:
["GET", "HEAD"]
​
reference_id
string | null

Filter data by reference ID.

Example:

"ad07c06f19054e484974fa22e9fb6bb1"

​
security_rule_names
string[]

Filter data by name of a security rule matched the request.

Maximum string length: 100
Example:
["SQL injection"]
​
results
enum<string>[]

Filter data by result.

Filter data by the event processing result.

Available options:
,
passed,
blocked,
suppressed
Example:
["passed", "blocked"]

Response

Successful Response

​
limit
integer
required

Number of items requested in the response

​
offset
integer
required

Items response offset used

​
count
integer
required

Number of items contain in the response

​
results
RequestSummary · object[]
required

List of items returned in the response following given criteria