Skip to main content
unbound download exports your organization’s data as CSV — the same exports offered in the dashboard, from the terminal. Requires Admin role. Run unbound status to check.

​
What can be exported

unbound download kinds also lists the filters each one accepts. It reads a list the CLI carries rather than asking the server, so a kind added to Unbound works before it appears here.

​
Export something

The command starts the export, waits for it, and saves the file. Without -o it writes a file named by the server in the current directory, and refuses to overwrite one that already exists.

​
Time range

Omit both and the server applies its own default window.

​
Filters

--search <text> matches free text, on the logs kinds only. Repeat --filter with the same key to pass a list. Each value is sent separately, which is how the server reads list filters:
An unknown filter key is silently ignored, so a typo widens the export rather than failing — tool_type=CURSOR returns every tool. An invalid value for a known key is rejected, with the accepted values listed. Run --check first and confirm the count moved.

​
Check before you export

--check counts the rows without starting anything:
An export of more than 25,000 rows is refused up front, with the real count, so narrow the range or add filters rather than paging.

​
If you stop waiting

A large export takes a few minutes. The job ID is printed when it starts:
Interrupting the wait does not cancel the export. Fetch the finished file within 6 hours:
--no-wait starts an export and returns the ID immediately, for a script that would rather collect it later:
Only 3 exports may be preparing at once per organization. A fourth returns an error asking you to wait — do not poll by re-running the export.

​
Output flags

​
For scripts and agents

An export is prepared by a background worker, so it is three steps: start it, poll until it is ready, then download it. unbound download start does all three and blocks until the file is on disk. Without -o, the destination depends on where output is going: a file named by the server when you are at a terminal, and stdout when it is piped or redirected. Diagnostics go to stderr either way, so the stream stays clean. The exit code is 0 on success and 1 on any error.
Requires CLI 1.15.0 or later. Tool Use data can also be exported with unbound analytics tool-use <dataset> --format csv, which uses this same flow — see Analytics.