Skip to main content
POST
Open a session
A build session is an isolated checkout of a workspace’s monorepo — the same concept as the Zite MCP sandbox. You create apps and edit files inside a session, then commit to build and version your changes. The response includes the workspace’s file tree, its apps, and the framework guide — the same spec agents receive, describing the project layout and conventions.
  • Every file and commit call takes the sessionId returned here.
  • Use one session per concurrent build so parallel jobs don’t clobber each other.
  • Sessions auto-stop after ~15 minutes idle and re-boot transparently on the next call.

Authorizations

Authorization
string
header
required

Enter your Zite API key. Format: Bearer <api_key>

Path Parameters

workspaceId
string
required

The workspace ID.

Response

The open session

sessionId
string

Pass this in the path of every session call. Opaque; encodes the workspace and an isolated checkout.

Example:

"sbx:wsp8bce4d1edc51710:2f0c9a1e-77f4-4b3e-9f2a-1c7b40e8d316"

workspaceId
string
Example:

"wsp8bce4d1edc51710"

apps
object[]
files
string[]

The workspace file tree, relative to the workspace root.

integrations
object[]

Integrations already connected to the workspace.

docs
object[]

Index of fetchable framework guides and recipes.

guide
string

The zitejs framework guide. Read it before writing app code.