Overview

The Orchestrator API is a stateless passthrough to the canonical Gizzi orchestrator running in Gizzi Runtime. The platform API preserves the HTTP method, path suffix, query string, request body, and response status so the orchestrator remains the single source of orchestration state. Live executor sessions belong to the Gizzi Node process, not the platform API.

Base URL

For local development:
The upstream target is the configured terminal server at /v1/orchestrator.

Authentication

All requests require a valid bearer token in the Authorization header. The platform also forwards Gizzi basic-auth credentials when GIZZI_PASSWORD or GIZZI_SERVER_PASSWORD is configured. See Authentication for details.

Endpoints

Proxy example

The platform forwards this to:

Streaming responses

If the upstream returns text/event-stream, the platform proxies the byte stream without buffering and sets the appropriate SSE headers:

Request body forwarding

JSON bodies are forwarded verbatim:

Response

Responses are proxied with the same status code and Content-Type returned by Gizzi Runtime. A successful request returns whatever the orchestrator returns; the platform does not reshape the body.

Error codes