OpenAPI specification
Download the OpenAPI 3.1 description of the Vitruve API to generate clients or import it into Postman.
The whole reference is also available as an OpenAPI 3.1 document, generated from the same source as these pages so the two never disagree.
https://vitruve-docs-prod.web.app/openapi.jsonUse it
- Postman or Insomnia: import the URL as an OpenAPI collection, then set an
X-API-Keyheader or the API key authorization. - Generate a client: feed the file to a generator such as
openapi-generatororopenapi-typescript. - Validate responses: use the examples as fixtures in your tests.
What it contains
- Every endpoint, its method, path and query parameters, with types, enums and defaults.
- The JSON request body of every write, with its required fields, and the optional
Idempotency-Keyheader of every create. - The
X-API-Keysecurity scheme. - The shared error responses.
- A realistic example response for each endpoint.
Response bodies are described by example rather than by full JSON schemas: entities are Prisma rows returned as stored, and the reference lists the fields you can rely on. Generated clients should treat bodies as loosely typed and ignore unknown fields.
Partner platforms have their own document, limited to the endpoints they can call: see Partner OpenAPI.
Moving from api-exports
The pre-v1 endpoints on api-exports.vitruve.fit stop on 2027-01-31. How GET /users and GET /vbt-workouts map to the /v1 endpoints.
Vitruve MCP server
Connect Claude, ChatGPT, Claude Code, Codex, Cursor, VS Code and other MCP clients to an organization's Vitruve data: read-only tools, OAuth sign-in, no API key.