events
Path parameters
Query parameters
(Optional): specifies the maximum number of results to return in a single response. By default - 20, max - 100.
(Optional): specifies the maximum number of results to return in a single response. By default - 20, max - 100.
Retrieves a detailed, paginated list of all requests processed by BotBye for a specific project. This endpoint provides comprehensive request-level data including headers, IP addresses, security check results, and decision outcomes, enabling deep forensic analysis and debugging.
Requires API key authentication:
This endpoint supports pagination and filtering parameters:
Pagination: See Pagination query parameters for details on first, after, last, before parameters
Filtering: Additional filters may be available for date ranges, request status, IP addresses, etc.
The response follows a cursor-based pagination pattern:
edges (array): Contains the request records
cursor (string): Pagination cursor for this record
node (object): The request data with the following fields:
pageInfo (object): Pagination metadata
hasPreviousPage (boolean): Whether there are more results before the current page
hasNextPage (boolean): Whether there are more results after the current page
startCursor (string | null): Cursor pointing to the first item
endCursor (string | null): Cursor pointing to the last item
total (integer): Total number of requests found
Security Investigation: Analyze specific requests to understand security decisions
Debugging: Troubleshoot why legitimate requests are being blocked
Audit Logging: Maintain comprehensive logs for compliance and security audits
Threat Analysis: Study attack patterns by examining declined request details
False Positive Analysis: Review blocked requests to tune security rules
Performance Monitoring: Track request patterns and identify bottlenecks
Customer Support: Investigate user-reported issues with specific requests
Forensic Analysis: Deep-dive into security incidents with complete request data
To retrieve the next page of results:
Data Volume: This endpoint can return large amounts of data; use pagination effectively
Headers: The headers field contains a JSON string that needs to be parsed
IP Addresses: remoteAddr shows the direct connection IP, while realIp shows the actual client IP (useful when behind proxies/CDNs)
Failed Requests: Check failedMessage and failedChecks to understand why requests were declined
Custom Fields: Use customFields to pass and retrieve application-specific data
Data Retention: Request logs are retained according to your BotBye plan
Performance: For high-traffic projects, consider filtering by date range to improve query performance
Privacy: Request data may contain sensitive information; handle according to your privacy policies
Filter by date range for better performance on high-traffic projects
Use isBanByRule: true to focus on rule-based blocks
Filter by country or asn to analyze geographic patterns
Combine filters to narrow down specific security events
(Optional): a cursor for pagination.
after (string): Pointer to the item after which the items are to be retrieved.before (string): Pointer to the item before which the items are to be retrieved.(Optional): is used to create conditions for data filtering. It can be used to create simple conditions (leaf nodes) as well as compound logical expressions (branch nodes).
predicate (string): The filtering condition (e.g., gte, lte, eq for a leaf or and, or for a branch). Possible values [[#Predicate]]opearands (string): A list of nested conditions (used only for branches, such as and, or).fieldPath (string): The field to which the filtering condition is applied (used only for a leaf. Each entity has its own fieldPath list).value (string): The value to compare against the field (used only for a leaf).(Optional): property by which to order by.
fieldPath (string): name of order field.direction (string): ASC or DESC