Automating Cooledge with the API and MCP

If you want software to read or update your Cooledge data, use an API key or a connected app. Do not give a script, bot or AI agent your email and password. Signing in with a script breaks whenever we change the sign-in flow, makes everything the software does look like you did it, cannot be switched off without changing your password and is not permitted under our Terms of Service.

The supported way

API keys. Go to Settings, open the Developers page and create a key. You choose what it can do: customers, jobs, quotes, invoices, bookings and leads, each as read or write, or one of the Read-only and Full access presets. Messages has its own row. Read lets the key read your conversations and messages. Write drafts (never sends) lets it write reply drafts for your team to check and send. The presets leave Messages out, so tick it yourself if you want it. Only the account owner can create or revoke keys and approve a connected app. Admins can see them but cannot create, revoke or disconnect anything. The key is shown once. You can hold up to 20 active keys and revoke any of them at any time. A revoked key stops working on its next request.

AI assistants. To connect Claude, Cursor, ChatGPT or another MCP client, add the Cooledge MCP server inside that client, using the server URL and per-client steps in the MCP guide. A Cooledge consent screen opens in your browser for the account owner to approve. The app then appears under Settings, then Developers, then Connected apps, where the owner can disconnect it at any time. Clients that cannot do OAuth use an API key instead. Every tool call is checked against the same plan, scopes and rate limit as the API, so an assistant can only do what you allowed. An assistant can read your conversations and draft replies only when it asks for them and the owner approves Read conversations and messages and Write message drafts (never sends) on the consent screen. It can never send a message. See Drafts from an AI assistant.

Webhooks. If you want to react to changes rather than poll, subscribe to events such as a quote being accepted, a booking being created, a text or email arriving or a message being sent from Messages. You manage subscriptions under Settings, then Integrations, then Webhooks. See the webhooks guide for events and payloads.

What the API covers today

Customers and their sites and contacts, leads, jobs and job phases, bookings, quotes (reading, updating, sending and creating ducted quotes), invoices (reading, adding lines and sending), conversations and messages (reading), message drafts (creating, updating and deleting) and webhooks. An app can write a reply as a draft, but it can never send it. A person on your team checks the draft and sends it. See Drafts and the Messaging API guide. The full reference is at cooledge.com.au/developers/reference.

Not yet available through the API: price lists and catalogues (other than the ducted unit list used for ducted quotes), suppliers and purchase orders, payments, sending messages, campaigns, reviews, files and photos, timesheets, reports and settings. If you need one of these, tell us. We would rather add it than have you work around it.

Plans and limits

The API and MCP are included on Growth and Scale plans, including the free trial. Each key can make 120 requests a minute. If that is not enough for your workflow, contact support.

Related

• Connecting Cooledge with the API and webhooks
• Developer documentation