Skip to main content
Exports create tracked artifacts with an export manifest. Table exports can be CSV or JSON, project data exports can be ZIP/CSV or JSON, and schema exports can be JSON or SQL. A project data export is a row extract; it is not a restorable SQLite database file.

​
Export types

Create table export

Create database export

Create schema export

Download export

Table and project data exports default to at most 5,000 rows per table. The configured maximum is 40,000 rows per table unless the installation changes that limit. Filters and a row limit can be supplied for each table. The manifest normally expires one day after creation; use its returned expires_at value as the authority for a particular export. New export manifests include sha256, the SHA-256 digest of the exact downloadable artifact bytes. Older manifests may return null. Check the digest after downloading when you need a verified copy. The panel’s table export form supports local date inputs for a chosen timestamp column. It converts the selected bounds to UTC and sends a half-open [from, to) filter. Choose the format that matches stored values: UTC ISO-8601 text, Unix milliseconds, or Unix seconds. For UTC text, the panel compares second-aligned UTC prefixes so values with or without fractional seconds at the boundary behave consistently. This controls which rows enter the bounded extract; it does not turn the artifact into a restorable SQLite snapshot. A result whose row_count equals the limit may have more matching rows. The panel’s project data export form can select one table and apply the same date filter. It can also export all tables without a date filter. Project data exports read the selected tables from a consistent database view and write rows incrementally, but each table still has a row limit. The returned row_count is the sum of exported rows; inspect each table in the JSON or ZIP manifest for its count. An authorized download returns the generated artifact bytes unchanged, including application column names and values. Treat the file as private project data. Interrupted downloads can resume with a single HTTP byte range and If-Range set to the previous ETag. Verify the assembled file against the manifest’s sha256 value. Authorization and export expiry are checked on every request.