Workspaces

Get a workspace

One workspace. An id this credential cannot see is a 404, the same as one that does not exist: another account’s, and — for an API key confined to a workspace — any workspace but its own.

A computer can carry the workspace_id of a workspace that has since been deleted, if the workspace was deleted while it still held computers, before that was refused; if a create or a snapshot clone into it was under way when it was deleted; or if it is a clone (POST /computers/{id}/clone) of such a computer, which keeps its source’s workspace_id. That id answers 404 here. One thing about such a computer is handled: its egress credentials resolve account-wide only, so an egress_proxy naming one of that workspace’s own secrets is held closed (egress_proxy_pending true) until it is saved again naming an account-wide secret. Such a computer can be moved to a live workspace, or to none, with PUT /computers/{id}/workspace or from the dashboard once its secret bindings and proxy credentials are removed and it meets the other conditions under GET /workspaces.

Requires the viewer role or higher.

get/workspaces/{id}

Request

  • Base URL: https://app.mandala.computer/api/v1
  • URL: https://app.mandala.computer/api/v1/workspaces/{id}
  • Auth: HTTP bearer

Path parameters

idstring required

The workspace id.

Response

The workspace.

idstring required

wsp- and twelve hex characters. What a computer’s workspace_id names.

namestring required

Its name, unique within the account. Up to 40 characters.

created_atstring required

RFC 3339 timestamp.

Changes

No recorded changes to this operation across all 1 revision of this API.