Skip to main content
The Trellis API surface is focused on secure workspace access for trusted integrations. Use it when an external system needs to create, read, update, or delete Trellis operational objects, or connect an AI client to approved workspace tools.
The public REST API covers CRUD access for tasks and properties, plus daily work orders and programmatic authentication. Other Trellis objects are available through documented MCP tools or by agreement with Trellis support. Do not build against undocumented endpoints.

​
Base URL

Use the production API host: 
https://api.trellistech.com
The hosted MCP endpoint is: 
https://api.trellistech.com/v1/mcp-server
The public REST API endpoint is served from the Trellis app host: 
https://app.trellistech.com/api/v1

​
Authentication

Every trusted request must include a Bearer token in the Authorization header. Use a workspace API key for server-side integrations, or a session access token from POST /api/v1/auth/token for programmatic user authentication: 
curl -H "Authorization: Bearer trls_acmevaca_abc123..." \
  https://app.trellistech.com/api/v1/workspaces/acme-vacations/properties
See Authentication for key management, session tokens, and security guidance.

​
Available integration surface

Public REST API

Create, read, update, and delete versioned task and property contracts with workspace API keys.

Trellis MCP Server

Connect MCP-compatible clients to Trellis tools.

Authentication

Workspace API keys and programmatic session authentication.

​
Contract versions

ContractVersion
Public REST APIv1
API contract1.4.0
OpenAPI document3.1.0
Tasks objecttasks.v1.3.0
Properties objectproperties.v1.2.0
Open the interactive REST reference at app.trellistech.com/public-docs.

​
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.
StatusMeaning
200Request succeeded
400Request was malformed
401API key is missing, invalid, expired, or not valid for the requested workspace
403Authenticated user does not have access to the requested workspace
429Too many requests
500Unexpected server error