Export API
Export traces, datasets, and eval runs in bulk. All export endpoints require API key authentication and respect project-scoped permissions.
GET /api/v1/export/traces
Export all traces for the project associated with the API key.
GET /api/v1/export/traces
Authorization: Bearer ts_...Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
format | string | No | json (default) or csv |
from | ISO 8601 | No | Start date filter |
to | ISO 8601 | No | End date filter |
status | string | No | OK or ERROR |
GET /api/v1/export/traces/[id]
Export a single trace with all its spans and scores.
GET /api/v1/export/traces/trace-abc-123
Authorization: Bearer ts_...GET /api/v1/export/datasets/[id]
Export a dataset with all its items.
GET /api/v1/export/datasets/dataset-abc-123
Authorization: Bearer ts_...GET /api/v1/export/eval-runs/[id]
Export an eval run with all its results.
GET /api/v1/export/eval-runs/evalrun-abc-123
Authorization: Bearer ts_...Response
All export endpoints return the data in the requested format. JSON responses follow the standard 2Signal envelope:
{
"data": [...],
"error": null
}Permissions
Export requires trace.export, dataset.export, or eval_run.export permission respectively. VIEWER+ roles have export permissions by default.
Rate Limits
Export endpoints share the same rate limits as other API endpoints. For large exports, consider using date range filters to paginate results.