Workspaces
Tenancy — organizations own workspaces, workspaces scope everything else.
A workspace is the container everything else lives in. Signals,
segments, models, pipelines, trainings, deployments, and goals belong to
exactly one workspace, and the X-Workspace-Id header on nearly every API
request names which one you're working in. An organization sits one
level up: it groups people and workspaces under shared membership, roles,
and billing.
Organization (people, roles, plan, billing)
└── Workspace (region-pinned data container)
└── signals · segments · models · pipelines
trainings · deployments · goalsYou don't need an organization — individual accounts own workspaces directly — but teams usually want one.
Thirty seconds of API
# Where does X-Workspace-Id come from? Right here:
curl "$API_BASE/v1/workspace" \
-H "Authorization: Bearer $TOKEN"
# Create a workspace
curl -X POST "$API_BASE/v1/workspace" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{ "name": "Demand forecasting" }'Routes in this section authenticate with Authorization alone — no
X-Workspace-Id needed. That's deliberate: you call these routes to
discover your workspace ID in the first place. See
Authentication.
In this section
Concepts
Scoping, organization roles, and regions.
Find your workspace ID
List your workspaces and pick the uid every other call needs.
Manage workspaces
Create, inspect, edit, and delete workspaces; pick a region.
Workspace members
Share a single workspace — list, add, and remove members.
Organizations
Create an organization, manage details, members, and roles.
Invitations
Invite people by email; verify, accept, or decline.
API tokens themselves live under Account; credits and quotas under Billing.