Getting started
Build integrations with the BlueSuite REST API, MCP tools, webhooks, and client forms
Connect your software or AI assistant to the same contacts, jobs, visits, and billing records your team uses in BlueSuite.
Choose a connection
| Use case | Start here |
|---|---|
| Build a server integration | REST API v1 and authentication |
| Connect an AI assistant | MCP setup and the tool reference |
| Receive changes from BlueSuite | Webhooks |
| Capture inquiries or offer booking on a website | Client forms |
| Maintain an older form integration | Legacy embedded forms |
Make your first API request
Create a REST API key in your workspace's integration settings with the scopes your integration needs. Store it in your server's environment as BLUESUITE_API_KEY.
curl 'https://my.bluesuite.app/api/v1/contacts?per_page=10' \
-H "Authorization: Bearer $BLUESUITE_API_KEY"This request needs contacts:read. Responses are scoped to the workspace belonging to the key. An API key is not needed for the public client-form endpoints.
Addresses
| Connection | URL |
|---|---|
| REST API | https://my.bluesuite.app/api/v1 |
| MCP, Streamable HTTP | https://my.bluesuite.app/api/mcp |
| Documentation for AI readers | llms-full.txt |
| REST request schemas | api-reference.json |
| MCP input and output schemas | mcp-tools.json |
Before writing data
Creating a quote or invoice does not send it. Recording a payment does not charge a card. Recurring job schedules control both future visits and per-visit billing. Read the relevant resource guide or MCP workflows before automating these operations.