---
title: "API Terms | ThriveDesk"
canonical: "https://www.thrivedesk.com/legal/api-terms/"
author: ThriveDesk
description: API Terms for ThriveDesk customers and site visitors.
categories: [legal]
---

# API Terms

Last updated: 6 October 2026

These terms apply when you or your developers connect to ThriveDesk through our API, MCP server, webhooks, the chat widget's JavaScript API or any other developer interface (together, "the API"). They add to our [Terms & Conditions](https://www.thrivedesk.com/legal/terms/) and [Acceptable Use Policy](https://www.thrivedesk.com/legal/acceptable-use-policy/).

## 1. Access

-   API access comes with your account. Some interfaces, such as the MCP server, are only available on certain plans.
-   Authenticate with the method we provide: API keys, OAuth or a sign-in you approve in your browser. Keep keys and tokens secret and rotate them if they may have leaked.
-   Everything done with your keys or approved connections counts as done by your account.

## 2. Limits

We set rate limits and usage limits to keep the service fast for everyone, and we publish them in our [documentation](https://help.thrivedesk.com/). Don't try to get around them, for example by spreading calls across several accounts. If you need more, contact us before you build.

## 3. What you may build

You may use the API to connect ThriveDesk to your own systems, automate your own support work, and build integrations for your own business or for other ThriveDesk customers.

You may not use the API to:

-   build a product that copies or replaces ThriveDesk's core features;
-   pull data in bulk to train AI models that are offered to third parties;
-   access data you aren't authorised to see;
-   send spam or do anything else the Acceptable Use Policy forbids.

## 4. Customer data

Data you pull through the API is still your customers' personal data. Store it securely, use it only for the purpose you collected it for, and delete it when you no longer need it. If you build an app other ThriveDesk customers install, tell them clearly what data it reads and where it goes.

## 5. AI clients and MCP

When you connect an AI client such as Claude or ChatGPT through our MCP server, that client's provider processes the data it reads under its own terms. Choose which clients you connect, and remove connections you no longer use from your settings.

## 6. Changes and deprecation

We improve the API over time. For changes that break existing integrations, we'll give at least 90 days' notice, except where a change is needed for security or legal reasons. Endpoints marked beta can change without notice.

## 7. Branding

You may say your integration works with ThriveDesk. Don't suggest that we built, endorse or certify it unless we've agreed to that in writing, and don't use our logo in a way that could confuse people.

## 8. Suspension

We may revoke keys, block a connection or suspend API access if it puts the service, our customers or their data at risk, or breaks these terms. Where we can, we'll contact you first.

## 9. No warranty

The API is provided as it is, without warranties beyond those in our Terms & Conditions. The limits of liability in the Terms apply to the API too.