Learn how to interact with workspaces in Mudstack using the API.
Workspaces in Mudstack are containers that organize and manage assets, libraries, tags, and other entities. Each workspace belongs to a specific account and is isolated from other workspaces. This means that all content within a workspace is accessible only through that workspace and cannot be shared across workspaces.
To interact with a workspace, you must include the following headers in every API request:
Without these headers, the API will not be able to identify the workspace or account, and the request will fail.
Workspaces contain several entities, each with its own sub-entities. These include:
Below are some common endpoints for interacting with workspaces:
Here is an example of how to retrieve the details of a workspace:
x-workspace-id
and x-account-id
headers are included in every request to avoid authorization errors.For more details on specific endpoints, refer to the API reference documentation for each entity.
Learn how to interact with workspaces in Mudstack using the API.
Workspaces in Mudstack are containers that organize and manage assets, libraries, tags, and other entities. Each workspace belongs to a specific account and is isolated from other workspaces. This means that all content within a workspace is accessible only through that workspace and cannot be shared across workspaces.
To interact with a workspace, you must include the following headers in every API request:
Without these headers, the API will not be able to identify the workspace or account, and the request will fail.
Workspaces contain several entities, each with its own sub-entities. These include:
Below are some common endpoints for interacting with workspaces:
Here is an example of how to retrieve the details of a workspace:
x-workspace-id
and x-account-id
headers are included in every request to avoid authorization errors.For more details on specific endpoints, refer to the API reference documentation for each entity.