API reference
Read the datasets Clickr keeps in sync from Buildertrend and QuickBooks, and run QuickBooks actions, over HTTPS. Every request goes to one base URL with your API key as a bearer token.
Request
curl https://api.clickr.cloud/v2/account \
-H "Authorization: Bearer $CLICKR_API_KEY"const response = await fetch(`https://api.clickr.cloud/v2/account`, {
headers: {
Authorization: `Bearer ${process.env.CLICKR_API_KEY}`,
},
});
const data = await response.json();import os
import requests
response = requests.get(
"https://api.clickr.cloud/v2/account",
headers={"Authorization": f"Bearer {os.environ['CLICKR_API_KEY']}"},
)
data = response.json()Response
{
"id": "66f0a1c2e4b0d1a2b3c40000",
"name": "Halvorsen & Styke Builders",
"email": "office@halvorsenstyke.example"
}From the sample builder, Halvorsen & Styke.
Ask Claude or ChatGPT about the same records: add https://api.clickr.cloud/mcp/playground as a connector, with no sign-in. Try it on a sample builder ›
Make your first request
In Clickr, open Settings and choose Create key under API keys. The key is shown once, so keep it somewhere safe. Send it in the Authorization header; this call returns the account the key belongs to. Authentication
What's in the API
Datasets
Read the records Clickr keeps in sync from your connectors, filtered, sorted and paged.
2 endpoints · 20 datasets
QuickBooks
Create, read and update projects, convert estimates to invoices and reactivate customers. Each call starts a run.
5 endpoints
Runs
Check on a QuickBooks action: queued, processing, then successful or failed, with what it did.
2 endpoints
Account
The account a key belongs to.
1 endpoint
MCP server
The same datasets and actions as tools, for Claude, ChatGPT and other assistants.
9 tools
The whole reference is also one OpenAPI 3.1 file, for Postman, code generators and assistants: clickr.cloud/developers/openapi.json