WAF analytics API — attack types and rule events

HackGATE’s managed proxy runs ModSecurity as its Web Application Firewall. These endpoints expose WAF telemetry so you can track which rules fired, which attack categories were detected, and how WAF activity changed over time. Use them to distinguish between genuine attack patterns and researcher noise during an engagement. All WAF analytics endpoints require a valid Bearer token in the Authorization header.

Common query parameters

string

required

The hackgatedName of the HackGATE site to query.

string

required

Start of the time range as an ISO 8601 date-time string (for example, 2025-07-01T00:00:00Z).

string

required

End of the time range as an ISO 8601 date-time string (for example, 2025-07-14T23:59:59Z).

WAF messages
Attack types
API coverage

GET /api/analytics/getWAFMessages

GET https://api-admin.hackgate.io/api/analytics/getWAFMessages

Returns the individual ModSecurity rule messages triggered on the site within the time range. Each record represents a rule match, including the rule ID, message, and the request that triggered it.

curl "https://api-admin.hackgate.io/api/analytics/getWAFMessages?url=my-site&gte=2025-07-01T00:00:00Z&lte=2025-07-14T23:59:59Z" \
  -H "Authorization: Bearer <token>"

GET /api/analytics/getWAFAttackTypes

GET https://api-admin.hackgate.io/api/analytics/getWAFAttackTypes

Returns a breakdown of detected attack categories with counts for each type. Attack categories are returned as human-readable strings:

Attack type
Cross Site Scripting (XSS)
SQL Injection (SQLi)
Local File Inclusion (LFI)
Remote Code Execution (RCE)
PHP Injection
Remote File Inclusion (RFI)

curl "https://api-admin.hackgate.io/api/analytics/getWAFAttackTypes?url=my-site&gte=2025-07-01T00:00:00Z&lte=2025-07-14T23:59:59Z" \
  -H "Authorization: Bearer <token>"

[
  { "type": "Cross Site Scripting (XSS)", "count": 142 },
  { "type": "SQL Injection (SQLi)", "count": 87 },
  { "type": "Local File Inclusion (LFI)", "count": 31 },
  { "type": "Remote Code Execution (RCE)", "count": 14 },
  { "type": "PHP Injection", "count": 9 },
  { "type": "Remote File Inclusion (RFI)", "count": 3 }
]

GET /api/analytics/getAPICoverage

GET https://api-admin.hackgate.io/api/analytics/getAPICoverage

Returns the set of API paths and HTTP methods that researchers accessed through the proxy, along with request counts. Use this to measure how much of your API surface was exercised during an engagement.

Query parameters

string

required

The hackgatedName of the site to query.

string

required

Start of the time range as an ISO 8601 date-time string.

string

required

End of the time range as an ISO 8601 date-time string.

Response

Returns an array of objects, one per unique path and method combination observed.

string

The URL path that was accessed (for example, /api/users).

string

The HTTP method used (for example, GET, POST).

number

Total number of requests to this path and method combination within the time range.

Example

curl "https://api-admin.hackgate.io/api/analytics/getAPICoverage?url=my-site&gte=2025-07-01T00:00:00Z&lte=2025-07-14T23:59:59Z" \
  -H "Authorization: Bearer <token>"

[
  { "path": "/api/users", "method": "GET", "count": 214 },
  { "path": "/api/users", "method": "POST", "count": 42 },
  { "path": "/api/products/123", "method": "GET", "count": 98 },
  { "path": "/api/admin/config", "method": "GET", "count": 7 }
]

Overview

Sites

Projects

Analytics

Account & Org

Account

Analytics

Billing

Organization

PIE

Projects

Sites

WAF analytics API — attack types and rule events

Common query parameters

GET /api/analytics/getWAFMessages

GET /api/analytics/getWAFAttackTypes

GET /api/analytics/getAPICoverage

Query parameters

Response

Example

​Common query parameters

​GET /api/analytics/getWAFMessages

​GET /api/analytics/getWAFAttackTypes

​GET /api/analytics/getAPICoverage

​Query parameters

​Response

​Example

Common query parameters

GET /api/analytics/getWAFMessages

GET /api/analytics/getWAFAttackTypes

GET /api/analytics/getAPICoverage

Query parameters

Response

Example