Skip to main content
bronto search returns at most 10000 events per call. To pull more, create an export job: Bronto runs the query in the background and gives you a file to download. The exports API reference describes the job on the platform side.

Create an export

The convenience flags build the request body for you: For anything they don’t cover, pass the body yourself with -f key=value or --input body.json, as with any resource. Check the request before creating anything:
The dataset name is already resolved to its id. \u003e is a JSON-escaped >.

Wait and download

Without --wait, create returns as soon as the job is accepted. With --wait, it polls the job until it’s COMPLETE or FAILED, backing off from 2 seconds to 30 seconds between checks. It gives up after --wait-timeout (default 15m) and exits non-zero with export_wait_timeout. A failed job exits with export_failed. --download <path> implies --wait and saves the finished export to that path:
The download comes from a presigned URL, and the CLI doesn’t send your API key to it. The file is written as delivered, with 0600 permissions. To query the export offline, feed it to bronto search --local. If the file is gzip-compressed, decompress it on the way in:

Manage export jobs

Exports can’t be updated. Create a new one instead.