workspaces

Manage Domo workspace contents via the /nav/v1/workspaces REST API.

19|13|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/stahura/domo-ai-vibe-rules --skill workspaces-stahura
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspaces
Source: https://github.com/stahura/domo-ai-vibe-rules/tree/main/skills/administration/workspaces
Command: npx skills add https://github.com/stahura/domo-ai-vibe-rules --skill workspaces-stahura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exposes a reverse-engineered Domo Workspace REST API to manage workspace contents via curl and a developer token.

Core Features & Use Cases

  • Add, remove, list, and search content (cards, pages, datasets, and other assets) within a workspace.
  • Work across multiple workspaces using the undocumented API endpoints described in the guidance.

Quick Start

Authenticate with your Domo developer token and run the sample script to add a card to a workspace.

Frequently Asked Questions about workspaces

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Domo workspace content programmatically using the REST API?

You can manage Domo workspace content programmatically by calling the reverse-engineered /nav/v1/workspaces REST API endpoints using curl and a valid X-DOMO-Developer-Token header to add, remove, list, and search assets.

Can I use a Domo developer token to automate workspace card management?

Yes, a Domo developer token can be used to automate workspace card management by passing it in the X-DOMO-Developer-Token header to authenticate REST API requests for adding, removing, and listing cards.

What's the best way to search for specific assets across multiple Domo workspaces?

The best way to search for assets across multiple Domo workspaces is using the undocumented /nav/v1/workspaces REST API endpoints, which require a valid developer token and the specific workspace GUIDs (UUIDs) to execute search operations.

Does the Domo workspace API require workspace GUIDs for content management operations?

Yes, the Domo workspace API requires workspace GUIDs (UUIDs) for content management operations, as these unique identifiers are necessary to target the correct workspace when adding, removing, listing, or searching cards, pages, and datasets.

What types of Domo content can I add or remove using the workspace REST API?

Using the workspace REST API, you can add, remove, list, and search various types of Domo content, including cards, pages, datasets, and other assets within your specified workspaces.

Why are my automated requests to the Domo workspace API failing?

Automated requests to the Domo workspace API may fail if the X-DOMO-Developer-Token header is invalid or missing, or if incorrect workspace GUIDs (UUIDs) are provided when targeting the /nav/v1/workspaces endpoints for content management operations.