Find a guide, feature, or API endpoint. Try “FTP”, “alerts”, or “instruments”.

Browse documentation

Docs/Developers

Read data and build exports

Inspect measurements in the dashboard and use the Developer API for your reporting and export workflows.

On this page

Use instrument graphs and tables for interactive review. Use the Developer API when another application needs to read project resources or measurement data, or when you need to build a repeatable export.

Inspect values in the dashboard

Open an instrument to review its variables, graph, and recorded values. Set an absolute time range when investigating a particular event. The values view can expose additional provenance details to authorized users, including source and run information.

For a shared view across instruments, create a dashboard with table and graph widgets. Choose aliases, units, precision, and aggregation to fit the audience’s question.

Use the Developer API

  1. Create a Query API connection and key with the required read permissions.
  2. Use the supported resource and measurement operations in the API reference.
  3. Resolve stable resource IDs and request a bounded time range.
  4. Follow pagination until the requested result is complete.
  5. Transform the returned data into your application’s format, such as CSV for a reporting workflow.

The current dashboard does not provide a general measurement CSV export or scheduled report builder. A custom export is an integration you build using supported API reads. The FTP Browser’s download action downloads upstream source files; it is a separate capability.

Preserve meaning in an export

Include the project, instrument and variable identifiers, labels, units, and timestamps needed to interpret the values. Keep timestamp offsets or an explicit timezone. Preserve null values as missing data instead of silently replacing them with zero.

If you use aggregated graph results, record the aggregation operation and interval. If you need individual recorded values, choose the data operation intended for that purpose. Check the operation’s response and pagination contract rather than assuming every API result is a flat table.

Historical and calculated data

Archived history must be requested through the applicable explicit history controls. During recalculation, previous current values can remain visible until the new result becomes current. Inspect recalculation status when an export must reflect a particular equation change.

For reproducible review, record the requested time bounds and the time you retrieved the data. Save the relevant calculation context alongside the export when it is part of your workflow.

See API authentication for key scope and the API reference for exact supported routes. Developer keys do not automatically grant access to every operation available in the browser dashboard.