Pagination

👍

This is important!

To get the best value out of your data feeds do pay close attention to the paging and sorting sections following. See the Pagination tutorial for more information.
We suggest that you first get your filtered searches worked out using the playground, and then use them in a script.

With the technicalities of pagination out of sight, you can concentrate on what is important - your data feeds!

Pagination: Retrieving the next batch of results

Each request may return up to 10 matching entities for your query. However, there may be more matches. To consume all the data, make sure you keep on calling the same URL string value that appears in the "next" key found in the output for each request.
We should distinguish between two cases in the DBD:
* Single Entity Result - which means that per parameter value the result shall be a single entity document with up to 100 leak records (references). The parameters relevant for this type of query are Email, Credit Card, Account name, Phone, SSN, Passport.
* Multi Entity Result - which means that per parameter value the result shall be multiple entitiy documents , up to 10 entities per page and up to 100 leak records per entity. the parameters relevant for this type of query are : bin6, bin8, domain.

JSON Output Example:

{

posts: [...],

totalResults: 7043729,

moreResultsAvailable: 7043629,

next: "/dbdocFilter?token=XXXXXXX-XXX-XXXX-XXXX-XXXXX[email protected]",

requestsLeft: 999932

}