Pagination and Filtering - FullHunt API Documentation

Pagination is endpoint-specific. Do not assume that every route accepts limit or returns pagination through response headers.

Common patterns

Pattern	Examples
`page` in query string	Enterprise alerts, suggested domains, certificates, impersonation records, Data Intelligence
`page` and `per_page`	Vulnerability intelligence feeds
Fixed page size	Enterprise typosquatting: 10; potential phishing: 1,000; OEM audit logs: 50; Global Search: 10
`limit`	Nexus and OEM WHOIS search, constrained to 1 through 10
Body pagination	OEM feeds, audit logs, and Global Search

Date filters

API	Format
Enterprise alerts, certificates, suggested domains, phishing, and typosquatting	`DD/MM/YYYY`
OEM audit logs	`YYYY-MM-DD`
WHOIS `expires_before`	ISO date or timestamp accepted by the endpoint

Similar filters with different names

Enterprise potential phishing and typosquatting use q.
Enterprise compromised credentials uses query.
Nexus company lookup uses query.
Nexus IP lookup uses query, while Tor lookup uses ip.
Domain Collection lookup uses domain.

Safe pagination loop

Start at page 1.
Validate that the expected items array and pagination object exist.
Process and deduplicate stable record identifiers.
Continue only while has_next, pages, or equivalent metadata indicates another page.
Set a maximum page count so malformed metadata cannot create an infinite loop.

See the brand impersonation guide and OEM metering guide for runnable pagination examples.