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

# Connect API overview

> REST reference for Connect: order-scoped threads with customer, merchant, and courier participants, lane-scoped messages, participant tokens, and lifecycle updates.

The Connect API manages **threads** — order-scoped conversations between a `customer`, a `merchant`, and a `courier`, supervised by your AI agent. Concepts are covered in the [Connect overview](/connect/introduction); this section is the REST surface.

All endpoints live under `https://api.open.cx/connect` and use [Bearer authentication](/api-reference/authentication).

## Resources

| Resource     | Endpoints                                                                                                                                                                                |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Threads      | [Create](/api-reference/connect/create-thread) · [Get](/api-reference/connect/get-thread) · [List](/api-reference/connect/list-threads) · [Update](/api-reference/connect/update-thread) |
| Participants | [Add](/api-reference/connect/add-participant) · [Remove](/api-reference/connect/remove-participant) · [Create token](/api-reference/connect/create-token)                                |
| Messages     | [Send](/api-reference/connect/send-message) · [List](/api-reference/connect/list-messages)                                                                                               |

## The two calls that matter

A full integration is thread creation at order confirmation and participant addition at courier assignment — the lifecycle, translation, moderation, and AI resolution run on their own. Everything else here exists for headless UIs, ops tooling, and audit.

## Idempotency

`POST /connect/threads` is idempotent on `reference` (your order ID): repeat calls return the existing thread with `200` instead of creating a duplicate. Design your order pipeline to fire-and-retry safely.