The Trellis API surface is currently focused on secure workspace access for trusted integrations, especially the Trellis MCP server. Use it when you want an external AI client or internal service to read Trellis operational context and, with confirmation, take approved actions in a workspace.Documentation Index
Fetch the complete documentation index at: https://docs.trellistech.com/llms.txt
Use this file to discover all available pages before exploring further.
Base URL
Use the production API host:Authentication
Every trusted request must include a workspace API key in theAuthorization header:
Available integration surface
Trellis MCP Server
Connect MCP-compatible clients to Trellis tools.
Workspace API keys
Create and rotate workspace-scoped keys for trusted server-side integrations.
What MCP tools can access
The hosted MCP server exposes Trellis operational tools for workspace data such as tasks, properties, reservations, conversations, workforce, knowledge base, and automations. Write actions are gated by the tool contract and should be paired with explicit user confirmation in your client.API keys are workspace-scoped. A key issued for one workspace cannot be used to operate on another workspace.
Status and errors
API responses use standard HTTP status codes. Include the request ID when contacting support about a specific call.| Status | Meaning |
|---|---|
200 | Request succeeded |
400 | Request was malformed |
401 | API key is missing, invalid, or expired |
403 | API key does not have access to the requested workspace |
429 | Too many requests |
500 | Unexpected server error |