Skip to content
SupaCloud Docs
Select themeSelect language

GET /api/me/active-workspace — the server-side active-workspace choice the web client reads at boot (#838 C6: the server value WINS over the per-browser localStorage cache, which is what makes the choice follow the user across devices and surfaces).

GET
/api/me/active-workspace
curl --request GET \
  --url https://example.com/api/me/active-workspace \
  --cookie supacloud_session=<supacloud_session>

Authorizations

Section titled “Authorizations”

Responses

Section titled “Responses”

200

Section titled “200”

The current user’s explicit active workspace

Media typeapplication/json

The current user’s explicit active workspace (GET /api/me/active-workspace).

object
workspace_id

null = no explicit choice yet (resolution falls back to the first membership), or the chosen workspace was since deleted.

string | null format: uuid
Examplegenerated
{
  "workspace_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0"
}

401

Section titled “401”

Authentication required

Media typeapplication/json

The canonical JSON body of every error response — the single source of truth the frontend binds to. Every AppError serializes as this exact shape, and the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is what the frontend error schema is generated from, so there is no hand-written error schema on either end.

object
code
required

Machine-readable, stable error code.

string
Allowed values: not_found unauthorized forbidden license_required license_expired bad_request unprocessable precondition_failed conflict method_not_allowed rate_limited too_many_requests quota_exceeded database_error docker_error vault_error internal_error
details
One of:
null
error
required

Human-readable message (the server’s English text; the client may localize by code).

string
Example
{
  "code": "not_found"
}

500

Section titled “500”

Structured server error

Media typeapplication/json

The canonical JSON body of every error response — the single source of truth the frontend binds to. Every AppError serializes as this exact shape, and the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is what the frontend error schema is generated from, so there is no hand-written error schema on either end.

object
code
required

Machine-readable, stable error code.

string
Allowed values: not_found unauthorized forbidden license_required license_expired bad_request unprocessable precondition_failed conflict method_not_allowed rate_limited too_many_requests quota_exceeded database_error docker_error vault_error internal_error
details
One of:
null
error
required

Human-readable message (the server’s English text; the client may localize by code).

string
Example
{
  "code": "not_found"
}