Content APIs
Import dashboard
Import dashboard to Omni instance.
POST
Import dashboard
Color palettes
If the export references custom color palettes, Omni resolves each referenced palette against the destination organization by exact (trimmed) name and type:- Identical colors — The existing palette is reused.
- Different colors, or more than one palette sharing that name with none matching by color — The import fails with
400before anything is written. The error message names the palette. - No matching palette — Omni creates one. Creating a palette during import requires the caller to have Editor or Manager permissions; otherwise, the import fails with
403before anything is written.
colorPalettes field lists which referenced palettes were created versus reused.
If a UUID doesn’t resolve to an existing palette in the destination organization, it’s dropped and the chart falls back to the organization’s default palette.
Presentation settings
document also carries any metadata.presentation object from the export (dashboard-level presentation settings, including the control bar’s collapsible / defaultExpanded / fixed state), which Omni writes onto the new workbook. Feature flags and generated descriptions from the source instance are not imported.
Tab keys
Import retains each tab’squeryIdentifierMapKey from the source dashboard by default, so tiles, filters, and tab references have the same key as the source. This lets a delivery or alert that addresses a specific tab in the source dashboard be recreated against the same key on the copy.
Set resetQueryIdentifierMap: true to renumber tabs 1, 2, 3... in the export’s ephemeral order instead.
An export without an ephemeral value has no source keys, so its tabs are still numbered 1, 2, 3... regardless of resetQueryIdentifierMap.Authorizations
Requires an Organization API Key. Personal Access Tokens (PATs) are not supported for this endpoint.
Include in the Authorization header as: Bearer ORGANIZATION_API_KEY
Body
application/json

