declined events summary
Retrieves a summarized breakdown of declined requests based on different analysis dimensions. This endpoint allows you to analyze blocked traffic by attack source, country, endpoint, reason, or rule, providing actionable insights for security optimization.
Endpoint
Authentication
Requires API key authentication:
Path Parameters
Query Parameters
Additional time-based filtering parameters are supported. See Pagination query parameters.
Response Structure
An array of summary rows. id, projectId and customerId are on every row; the rest depend on
type.
Common Properties (All Summary Types)
The five declined summaries additionally carry declinedValidationEventsCount (integer): the number
of declined requests for that row.
Summary Type: attack_source
Declined requests by IP address and country of origin.
Example Response:
Summary Type: country
Declined requests grouped by country.
Example Response:
Summary Type: endpoint
Declined requests grouped by endpoint.
Example Response:
Summary Type: reason
Declined requests grouped by the reason for blocking.
Example Response:
Summary Type: rule
Declined requests grouped by the rule that decided them. This summary also reports what the rule let through.
Example Response:
Summary Type: total_endpoint
Total traffic per endpoint, with the trend against the previous period. This summary reports totals
rather than declines, so it carries no declinedValidationEventsCount.
Example Response:
Use Cases
- Threat Intelligence: Identify top attack sources by IP and country
- Geographic Analysis: Understand which countries generate the most malicious traffic
- Endpoint Protection: Identify which endpoints are most frequently targeted
- Rule Optimization: Analyze which security rules are most effective
- Attack Pattern Analysis: Understand common reasons for request blocking
- Whitelist Management: Identify legitimate traffic that may need whitelisting
- Security Reporting: Generate detailed reports on attack patterns
Important Notes
- The
typequery parameter is required and determines the response structure - Results are typically ordered by
declinedValidationEventsCountin descending order (most declined first) - Use this endpoint to drill down into specific aspects of your declined traffic
- Combine with time filters to analyze trends over specific periods
- Country codes follow ISO 3166-1 alpha-3 standard (e.g., USA, DEU, GBR)
Accepted permissions
Project → Project → InfoToken scope
Project View
Authentication
Personal access token. Create it in your BotBye account under Profile → Personal Access Tokens, tick the scopes the endpoints you call require (see each endpoint’s Token scope), and send the token in the X-Api-Key request header. A token works only for the account it was created in.
Path parameters
Query parameters
(Required) attack_source, country, endpoint, total_endpoint, reason, rule
(Optional) Size of the lookback window, counted in interval_type units back from now. The default value is 1, meaning the current day (or the current hour if interval_type is HOUR). A negative value is rejected.
(Optional) Unit of the lookback window: HOUR or DAY, case-insensitive. Defaults to DAY. Any other value is rejected.
Response headers
Response
success - attack source summary

