> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omni.co/llms.txt
> Use this file to discover all available pages before exploring further.
## Submitting Feedback
If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:
POST https://docs.omni.co/feedback
```json
{
"path": "/api/content-migration/import-dashboard",
"feedback": "Description of the issue"
}
```
Only submit feedback when you have something specific and actionable to report.
# Import dashboard
> Import dashboard to Omni instance
This API is in beta and may have future breaking changes.
## OpenAPI
````yaml /api/openapi.yaml post /unstable/documents/import
openapi: 3.1.0
info:
title: Omni API
description: >
The Omni REST API provides programmatic access to your Omni instance for
managing users, documents, queries, schedules, and more.
version: 1.0.0
contact:
name: Omni Support
url: https://docs.omni.co
servers:
- url: https://{instance}.omniapp.co/api
description: Production
variables:
instance:
default: blobsrus
description: Your production Omni instance subdomain
- url: https://{instance}.playground.exploreomni.dev/api
description: Playground
variables:
instance:
default: blobsrus
description: Your playground Omni instance subdomain
security:
- bearerAuth: []
- orgApiKey: []
tags:
- name: AI
description: AI-powered query generation
- name: API Tokens
description: >-
Manage API tokens (Organization keys, Personal Access Tokens, MCP OAuth
grants)
- name: Connections
description: Manage database connections
- name: Connection environments
description: Manage connection environments database connections
- name: Content
description: Unified content retrieval (documents and folders)
- name: Content migration
description: Export and import dashboards
- name: Content validator
description: Validate content against models and perform find/replace operations
- name: Dashboard downloads
description: Download dashboards and tiles as PDF, PNG, XLSX, CSV, or JSON files
- name: Dashboard filters and controls
description: Read and update dashboard filter and control default values
- name: dbt
description: Manage dbt configuration for connections
- name: Documents
description: Create, retrieve, and manage documents
- name: Document favorites
description: Favorite and unfavorite documents
- name: Document labels
description: Apply and manage labels on documents
- name: Document permissions
description: Manage document-level access
- name: Labels
description: >
Manage labels in an organization. Labels can be applied to documents and
folders to help organize and categorize content.
**Label types:**
- **Basic labels**: Can be created and managed by any user
- **Verified labels**: Indicate curated or officially sanctioned content.
Admin-only.
- **Homepage labels**: Appear on the organization homepage. Admin-only.
- name: Folders
description: Create and organize content folders
- name: Folder permissions
description: Manage folder-level access
- name: Jobs
description: Check status of asynchronous jobs
- name: Models
description: Create and manage data models
- name: Model branches
description: Manage model branches and merge changes
- name: Model git configuration
description: Manage git configuration for shared models
- name: Queries
description: Execute workbook queries
- name: Schedules
description: Create and manage scheduled tasks
- name: Schedule recipients
description: Manage schedule recipients
- name: Schema refresh schedules
description: Manage automated schema refresh schedules for connections
- name: Topics
description: Retrieve topic information from models
- name: Uploads
description: Manage file uploads
- name: Users
description: Manage users
- name: User attributes
description: Manage user attribute definitions
- name: User groups
description: Manage user groups
- name: User model roles
description: Manage model and connection role assignments for users
- name: User group model roles
description: Manage model and connection role assignments for user groups
- name: Uploads
description: Manage CSV and spreadsheet uploads
paths:
/unstable/documents/import:
post:
tags:
- Content migration
summary: Import dashboard
description: Import dashboard to Omni instance
operationId: importDashboard
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- baseModelId
- dashboard
- document
- workbookModel
- exportVersion
properties:
baseModelId:
type: string
format: uuid
description: Target model ID
dashboard:
type: object
description: Dashboard configuration from export
document:
type: object
description: Document metadata from export
workbookModel:
type: object
description: Workbook model from export
exportVersion:
type: string
enum:
- '0.1'
description: Export format version (must be "0.1")
identifier:
type: string
description: Custom identifier for the imported dashboard
folderPath:
type: string
description: Destination folder path
fileUploads:
type: array
description: >-
Spreadsheet file data to restore during import. Include the
`fileUploads` array from the export response to restore
spreadsheet tiles in the imported dashboard.
items:
type: object
properties:
fileUploadId:
type: string
description: Unique identifier for the file upload (from export)
fileName:
type: string
description: Original file name
contentType:
type: string
description: MIME type of the file
data:
type: string
description: Base64-encoded file content
responses:
'200':
description: Dashboard imported successfully
content:
application/json:
schema:
type: object
properties:
dashboard:
type: object
properties:
dashboardId:
type: string
format: uuid
miniUuidMap:
type: object
workbook:
type: object
'400':
$ref: '#/components/responses/BadRequest'
security:
- orgApiKey: []
components:
responses:
BadRequest:
description: Bad Request - Invalid parameters or request body
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
schemas:
Error:
type: object
properties:
error:
type: string
description: HTTP response code for the error
example:
message:
type: string
description: Detailed error description
example:
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
description: >
Can be either an [Organization API
Key](/api/authentication#organization-api-keys) or [Personal Access
Token (PAT)](/api/authentication#personal-access-tokens-pat).
Include in the `Authorization` header as: `Bearer YOUR_TOKEN`
orgApiKey:
type: http
scheme: bearer
bearerFormat: JWT
description: >
Requires an [Organization API
Key](/api/authentication#organization-api-keys). Personal Access Tokens
(PATs) are not supported for this endpoint.
Include in the `Authorization` header as: `Bearer ORGANIZATION_API_KEY`
````