Skip to main content
Connect a trusted service to Trellis with the Public REST API, or let an external AI client use Trellis through the MCP Server. Both connections stay within the workspace and permissions granted to their credentials. Start by creating a workspace API key in Settings > Developer. Use a separate key for each integration, select the permissions it needs, then make a read request before enabling changes.

Base URL

Trellis API host:
The hosted MCP endpoint is:
The public REST API endpoint is served from the Trellis app host:

Authentication

For server integrations, send the workspace API key as a Bearer token in the Authorization header. Programmatic user sessions use the access token returned by POST /api/v1/auth/token; check the operation reference for its supported authentication methods:
See Authentication for key management, session tokens, and security guidance.

Available integration surface

Public REST API

Build integrations for tasks, properties, scheduling, supplies, and workflows using documented operations.

Trellis MCP Server

Connect MCP-compatible clients to Trellis tools.

Authentication

Workspace API keys and programmatic session authentication.

Contract versions

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.
Each key belongs to one workspace. Use a separate key and connection for each additional workspace; changing a workspace ID in a request does not grant access to it.

Status and errors

Read the error response before retrying. Fix invalid fields or missing permissions first; when an update conflicts with newer data, fetch the record again and review the change. API responses use standard HTTP status codes. Include the request ID when contacting support about a specific call.