Overview
Exports are asynchronous and use raw job snapshots rather than the standard envelope. Use exports when a search result set is too large for interactive pagination or when another system needs a durable CSV, JSONL, text, HTML, or JSON file. Thetype field selects the export family (docs, victims, or breach), while service tells OathNet which search service should produce the rows.
The export workflow has the same mental model as other long-running jobs:
- create a job from a search family, output format, fields, limit, and
query_config - poll until the job is complete, failed, or expired
- download the generated file while it is still available
- use list history to avoid creating duplicate exports
Successful create responses return HTTP
202 with a raw job snapshot.Create And Poll
Create Response Example
Completed Response Example
Notes
- Use
servicevaluesstealer,victims, orbreachfor current requests. - Use
query_configwhen the export should reuse the same structured filter grammar as search, bulk search, or scanners. listandstatusresponses are raw snapshots, not envelopes.downloadreturns a file stream. Save bytes directly.
Structured Filters
Reuse the same
query_config grammar across search, scanners, and exportsBulk Search
Run one search shape across many terms before exporting
Pagination
Use interactive pagination before switching to async exports
API Reference
Use OpenAPI for exact job schema, formats, statuses, and download behavior