Quick create a dataset with all its data requests in one go.
name as the canonical dataset name.dimension, metric, metricOperation, dateField, dateFormat, conditions, and legend are still accepted for compatibility, but new chart-specific bindings should be added to chartDatasetConfigs[] on the chart quick-create flow instead of the dataset.Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
ID of the team
Create a dataset with all its data requests in one API call. This endpoint is dataset-focused. Per-chart bindings should be configured on ChartDatasetConfig when creating or updating charts.
ID of the team
Array of project IDs where members can access the dataset
Whether the dataset is a draft and should be hidden from dashboard viewers
Canonical dataset name.
[Legacy compatibility] Dataset-level xAxis fallback. New per-chart bindings should be set on chartDatasetConfigs[].xAxis.
[Legacy compatibility] Dataset-level yAxis fallback. New per-chart bindings should be set on chartDatasetConfigs[].yAxis.
[Legacy compatibility] Dataset-level yAxisOperation fallback. New per-chart bindings should be set on chartDatasetConfigs[].yAxisOperation.
none, count, count_unique, sum, avg, min, max [Legacy compatibility] Dataset-level dateField fallback. New per-chart bindings should be set on chartDatasetConfigs[].dateField.
[Legacy compatibility] Dataset-level dateFormat fallback. New per-chart bindings should be set on chartDatasetConfigs[].dateFormat.
[Legacy compatibility] Previous dataset name field. Prefer name for reusable dataset naming.
[Legacy compatibility] Dataset-level filter fallback. New chart-specific filters should be set on chartDatasetConfigs[].conditions.
Schema of the fields in the dataset key(field name) => value(type). This gets populated automatically whenever the dataset is used in a chart.
Join settings for the dataset. Use indices (0-based) in joins array to reference data requests before they are created.
Array of data requests to create with the dataset
Index (0-based) of the main data request in the dataRequests array. Defaults to 0.
Variable bindings for the dataset. The entity_type and entity_id will be automatically set.
Created dataset with all data requests
Canonical dataset name. Prefer this over legend when referring to the reusable dataset itself.
[Legacy compatibility] Dataset-level binding fallback. New chart bindings should be stored on ChartDatasetConfig.
[Legacy compatibility] Dataset-level binding fallback. New chart bindings should be stored on ChartDatasetConfig.
[Legacy compatibility] Dataset-level binding fallback. New chart bindings should be stored on ChartDatasetConfig.
[Legacy compatibility] Dataset-level binding fallback. New chart bindings should be stored on ChartDatasetConfig.
[Legacy compatibility] Dataset-level binding fallback. New chart bindings should be stored on ChartDatasetConfig.
[Legacy compatibility] Dataset-level binding fallback. New chart bindings should be stored on ChartDatasetConfig.
[Legacy compatibility] Previous dataset name field. Prefer Dataset.name for reusable dataset naming.