Build API - Zite Platform

Base URL and auth

https://api.zite.com/v1

Authenticate with a Bearer API key from your Developer settings:

Authorization: Bearer <your-api-key>

The key acts as you — it can only see and change workspaces you have access to, and every change is attributed to you in the app’s version history.

The lifecycle

Create a workspace

A database plus the apps built on it. See Create a workspace.

Open a build session

An isolated checkout where you create apps and edit files. See Open a session.

Create an app and write code

Scaffold, edit, check, iterate. See Create an app.

Commit

Builds a versioned snapshot in the background. See Commit.

Deploy and observe

Publish the build live and pull logs. See Publish a deployment.

Relationship to the Zite MCP

Same operations and semantics as the Build MCP tools (a session maps to a sandbox) — use the MCP for interactive agents, the Build API for CI, scripts, and automation.

Conventions

Errors

Every error returns the same envelope:

{ "statusCode": 404, "error": "Not Found", "message": "App not found" }

Status	Meaning
`401`	Invalid or missing API key
`402`	The build tools aren’t included in your organization’s plan
`404`	Resource doesn’t exist
`409`	The workspace has newer commits than your session — pull and rebase inside the session, then commit again
`400`	Invalid request data, or publishing while the latest build was still `building` or had failed

Async builds

commit and publish kick off builds in the background. Poll the app’s buildStatus (see Get an app) and wait for a green build before publishing — publishing early returns a 400 explaining why.

​Base URL and auth

​The lifecycle

​Relationship to the Zite MCP

​Conventions

​Errors

​Async builds

Base URL and auth

The lifecycle

Relationship to the Zite MCP

Conventions

Errors

Async builds