Start here

Reference

Reference

The exact technical contract of Volobox: the HTTP API, the MCP server, webhooks and events, and the formats of manifests, workflows, apps and skills.

The reference is the exact contract: endpoints, headers, payloads, file formats, fields and commands, written for someone writing code against Volobox. For how to do a job end to end, start with the guides; for what an area is for, see the overview.

HTTP API

Volobox has a versioned public HTTP API under /api/v1/. Every call carries a bearer token, and acts with the permissions of the person, or the integration, it belongs to.

Note

The endpoint pages and the event catalog are generated from the API description and the event catalog in the product, so they change when the product does. The full OpenAPI description, with every request and response schema, is served by your own workspace to signed-in callers.

MCP and events

  • MCP server: the hosted endpoint, OAuth discovery, client registration, tool naming and the tools it offers.
  • Webhooks: what a delivery contains, how it is signed, and when it is retried.
  • Event catalog: every event Volobox can deliver to a webhook.

Formats

For AI tools

Every docs page has a plain Markdown version at the same address with .md added, such as /docs/api-overview.md. The site also publishes /llms.txt, a list of every page with a one-line description, and /llms-full.txt, all pages in one file.

Last verified against the product