Switchboard
  • Understand Switchboard
  • Build for Switchboard
  • Operate
  • API reference
Information
Manifest
    Get the manifest schemagetValidate a manifestpost
Releases
    List releasesgetCreate a releasepostGet a releasegetBegin testingpostRequest approval for productionpostApprove and shippost
Regression suites
    Get the regression suitegetGenerate the regression suitepostDispatch agents on the pending stepspostReport a step resultpost
GraphQL
    The control plane's GraphQL APIpost
Other endpoints
    Health checkgetInbound webhooks (GitHub App, Frontegg, partners)post
powered by Zuplo
Switchboard API

Switchboard API

Switchboard's primary API is GraphQL at AppSync, reached through this gateway (every console read and mutation — connections, repositories, environments, instances, builds, channels — lives there; see the design's D1). This REST surface is deliberately narrow: the operations that need callers with no GraphQL client. Two use cases: the release process — what QA tooling, the operation-phase plugin, and regression agent runners drive — and manifest validation for CI. Every operation is a stub returning an example payload; construction replaces the stub handler with the real resolver path and adds the require-auth inbound policy per routes-and-policies.md.

Tags
Manifest
CI-facing: validate a switchboard.yaml without a GraphQL client — a repo lints its manifest on every push.
Releases
The release process: assemble from channel heads, hold an environment, test, request approval, ship. The QA implementation team's surface — and the operation-phase plugin's.
Regression suites
Generated from what ships; steps run as guided human tests or agent runs, and every result carries evidence — a screenshot of the run.
GraphQL
Servers
https://switchboard-api-main-0076d17.zuplo.app