> ## Documentation Index
> Fetch the complete documentation index at: https://developers.cconnect.online/llms.txt
> Use this file to discover all available pages before exploring further.

# Build with Cconnect

> Connect your systems to Cconnect Desk and Chat.

Use the Cconnect Customer API to synchronize support tickets, read conversations and messages, discover your company's connected channels, and send WhatsApp messages or email ticket replies.

The API uses HTTPS, JSON, versioned resource paths, and company-owned bearer credentials. Each request is restricted to the company that issued its credential. Your credential's scopes and your company's product entitlements determine which operations you can use.

## What you can integrate

| Product | Supported operations in v1 |
| - | - |
| Desk | List, retrieve, create, and update tickets; read custom ticket fields and email channel metadata; send ticket email replies |
| Chat | Read conversations, message history, and WhatsApp channel metadata; send text and approved templates |
| Integration | Inspect your credential's company, scopes, and current products |

Creating an API ticket does not send a message or email. Use the [messaging guide](https://developers.cconnect.online/guides/send-messages.md) for explicit sends and status lookup. SMS, customer webhooks, bulk deletion, member administration, contact CRUD, and Call APIs are outside this release.

## Start here

* Follow the [quickstart](https://developers.cconnect.online/quickstart.md) for your first request.
* Ask your company administrator for a credential with the appropriate [scopes](https://developers.cconnect.online/authentication.md).
* Open the **API reference** tab for endpoint schemas and examples.
* Download the [generated OpenAPI specification](https://developers.cconnect.online/openapi.json).

## Addresses and availability

The developer portal is `https://developers.cconnect.online`. The specification is configured for the API origin `https://cconnect.online`; your Cconnect deployment administrator must confirm that this origin routes `/api/v1` to the updated Omni API before onboarding integrations.

The customer API and its messaging feature are disabled by default on the backend. These documents describe the v1 implementation; publication alone does not activate it. If a request returns `503 api_disabled`, ask your Cconnect deployment administrator to enable customer API access. Sending also requires messaging enablement; otherwise it returns `503 messaging_disabled`.

The resource-oriented reference follows conventions familiar from [Freshdesk](https://developers.freshdesk.com/api/) and [Qontak](https://docs.qontak.com/). Cconnect defines its own authentication scheme and supported operations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.