Overview
Bulk search is for batched investigations where one search shape needs to run against many terms. Instead of sending hundreds of separate search requests, you create one job with a sharedquery_config and a list of terms.
Use bulk search when:
- you have many domains, emails, usernames, or identifiers to check
- each term should reuse the same service, fields, filters, and output format
- you want an asynchronous job with status polling and a downloadable result
How It Works
- create one job with the shared search shape and all target terms
- poll the job until it finishes
- download the generated output file
- list recent jobs when you need history or recovery after a client restart
success/data envelope; list and status responses are raw JSON snapshots.
Query Config
query_config is the reusable part of the search. It can contain the same flat
filters and structured filter grammar used by normal V2 search.
service values are stealer, docs, victims, and breach.
Supported format values are csv, json, jsonl, txt, and html.
Polling
Bulk jobs may includenext_poll_after_ms. Prefer that value when present, and
fall back to a conservative interval when it is missing.