OpenAPI and Postman
Use the machine-readable contracts when building clients, test suites, monitors, or agent integrations.
OpenAPI
The OpenAPI 3 contract describes the current HTTP API, public media routes, OAuth metadata routes, MCP transport routes, and MCP HTTP gateway routes.
The contract includes route tags, request schemas, response schemas, auth schemes, and public-vs-protected route information.
Postman Collections
Workshop maintains two Postman collections in the main platform repository:
| Collection | Audience |
|---|---|
Workshop API.postman_collection.json |
Full internal/staging collection including admin, bootstrap, OAuth, MCP transport, and unhappy-path examples |
Workshop API (Public).postman_collection.json |
Public developer collection without internal bootstrap/admin routes |
The public collection includes folder guides, happy-path examples, and unhappy-path examples for each major route group.
Recommended Checks
Before integrating against a deployment:
- Run
GET /healthwithout auth. - Run
GET /api/healthwith an API key. - Compile a minimal
.wssource. - Queue a short native render.
- Poll
GET /api/render/{id}until complete. - Download
GET /api/video/{id}. - If using agents, mint a bearer token and call
GET /api/mcp/tools.
Next Steps
- Authentication - credentials and auth schemes
- MCP - agent-facing surfaces
- Render - end-to-end render flow