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
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:
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:
0600 permissions: NDJSON, one event per line,
compressed with zstd. The URL must use https, unless
your base_url is plain http (a local or dev instance). The file appears at the path
only once the download is complete: if the transfer fails, an existing file is left
untouched and no partial file remains. The timeout setting limits how long the server
may go without sending data, not the length of the whole download.
To query the export offline, decompress it on the way into
bronto search --local:
