Skip to Content
PlatformFeaturesData Exports

Data Exports

Data Exports run a SQL query against your Asset Inventory data and write the result to object storage as Parquet, JSONL, or CSV. Run an export once on demand, or attach a cron schedule to have it run automatically. Each run produces a downloadable file.

Data Exports is an Enterprise feature. When it is enabled for your plan, a Data Exports entry appears under Data Pipelines in the sidebar. Exports are user-scoped: any user manages their own exports, while administrators can view and manage every user’s exports.

Creating an Export

  1. In the sidebar, open Data Pipelines → Data Exports.
  2. Click New export.
  3. Enter a Name to identify the export.
  4. Enter the Query to run (for example SELECT * FROM aws_ec2_instances). The query is validated and authorized against your roles, so it can only read data you are allowed to see.
  5. Select a Format: JSONL, CSV, or Parquet.
  6. For CSV, optionally set a Delimiter and whether to Include header.
  7. Optionally set a Schedule (see Scheduling). Leave it empty for an on-demand export.
  8. Click Create. You are taken to the export’s detail page.

Formats

FormatDescription
JSONLOne JSON object per line.
CSVComma-separated values, with a configurable delimiter and optional header row.
ParquetColumnar format, best for large results and downstream analytics.

The CSV delimiter and header options apply only to CSV exports; they are ignored for JSONL and Parquet.

Scheduling

A schedule is a standard cron expression, interpreted in UTC (for example 0 6 * * * for 06:00 daily). The same rules as sync schedules apply, including a five-minute minimum between runs. An export with a schedule is enabled by default and shows its next run time.

  • Clearing the schedule disables the export and removes its pending next run.
  • An export cannot be enabled without a schedule.

Runs

Open an export to see its Runs tab:

  • Run now enqueues a run immediately, independent of the schedule.
  • Each run shows its status (created, started, completed, failed, or cancelled), rows written, creator, and time. In-progress runs update automatically.
  • A completed run has a Download button for its file. The download link is short-lived.
  • Delete removes a run and its exported file.

Editing and Deleting

The Edit tab updates the name, query, format, CSV options, and schedule. Deleting an export from the detail page permanently removes the export definition and all of its runs.

Downloading the Latest Export via the API

To fetch the most recent completed export in a single request — for example from a scheduled job — call the latest-download endpoint with a Workspace API key. It redirects to a short-lived presigned URL, so follow redirects:

curl -L -H "Authorization: Bearer <YOUR_API_KEY>" \
  "https://<YOUR_PLATFORM_URL>/api/table-export-definitions/<DEFINITION_ID>/runs/latest/download" \
  -o export.jsonl

The endpoint is keyed by the export’s ID, not its name — names are not unique. The export’s detail page shows a ready-to-copy version of this command with the ID filled in.

An API key authenticates as itself, not as the user who created it, so it can reach an export only when it is the export’s owner or has global access. In practice, use an Admin key (Admin:Read or Admin:Write): admin keys have global access and can download any export. A General key (General:Read or General:Write) can only download exports that key created itself, and CI / Schema Only keys have no access — a key without access gets a 404. Only Admin:Write users can create API keys, so downloading a dashboard-created export over the API is an admin-key operation.

Programmatic access

Data Exports can be managed via the Platform API. See the Platform API Reference (table-exports section) for endpoint details, including creating definitions, triggering runs, and downloading results.

Was this page helpful?

Last updated on

Full Report ExampleAlerts