> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://api.logicdialog.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://api.logicdialog.ai/_mcp/server.

# Authentication

| API area                                                  | Credential                                                                                                                           | Scope                                                                                |
| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------ |
| Send application messages and fetch client history        | Channels API token in `Authorization: Bearer TOKEN`                                                                                  | Deployed workspace, Live environment, API client and allowed channels                |
| Schedule calls/SMS and read their delivery state          | Channels API token in `Authorization: Bearer TOKEN`                                                                                  | Deployed workspace/environment, API client and explicitly allowed outbound schedules |
| Workspace configuration, knowledge, review and deployment | Kinde API access token in `Authorization: Bearer TOKEN`, or LogicDialog's HTTP-only `ld_session` cookie for same-origin app requests | Workspace membership and the operation's required permissions                        |
| Platform administration                                   | Platform authentication plus default-organisation admin permissions                                                                  | Administration scope, not just a workspace role                                      |
| Incoming approved-reply webhook at your server            | `LogicDialog-Signature`, verified with your client's outbound signing secret                                                         | Authenticity of the exact webhook body                                               |
| Widget session                                            | Enabled integration and allowed browser `Origin`, followed by an issued capability                                                   | One widget session                                                                   |
| Provider ingress                                          | Provider-specific signature or capability                                                                                            | Selected transport                                                                   |

## Channel API keys

Generate credentials under [Project → Channels → API](https://app.logicdialog.ai/channels?tab=api). Copy both values before saving. The **API token** authenticates your requests; the **signing secret** verifies callbacks from LogicDialog. They are different credentials and are not interchangeable.

Deploy the configuration to Live before testing. Include `workspaceId`, `environment=live` and `integrationId` on each [message](/api-reference/messaging-and-history/post-channels-messages) or [history](/api-reference/messaging-and-history/get-channels-conversations-conversation-id) request. Requests from a different client cannot read or continue your conversations. A token is a server-side integration credential: keep it out of customer-facing JavaScript and mobile application bundles.

API keys cannot add knowledge, approve changes or deploy environments. Those operations currently require platform authentication. There is no channel-key knowledge upload endpoint or channel-key permission for publishing.

For outbound calls/SMS, select the permitted schedules by name under **Allowed outbound schedules** for the client. Existing keys have no outbound permission until explicitly granted. Clients used only for outbound contacts can leave message channels empty and do not require a reply webhook or signing secret. See the outbound examples in the workflows guide.

## Platform authentication

Browser login starts at [Sign in](/api-reference/authentication/get-auth-login); the callback establishes a LogicDialog session. Server-side callers need a valid Kinde access token issued for the platform's configured issuer/audience. Ask the platform administrator to provision the identity and workspace/organisation permissions. The API does not provide a channel-key-to-platform-token exchange or a public endpoint to mint management credentials.

The hosted explorer cannot reuse the parent application's cookie. Select **PlatformBearer** and supply the authorised access token. Do not paste a Channels token, a Fern publishing token, or an AI provider API key into that field.

Common permissions are `workspace.view` for reading configuration, `workspace.edit` for editing/ingestion, `conversations.review` for staff history and Live Chat, and `integrations.manage` or `workspace.manage` for Channels. Applying a workstream needs **both** `changes.approve` and `deploy.test` or `deploy.live`, according to the destination.

## Errors

* **400**: invalid fields, missing branch, or an unsupported write to Live/main.
* **401**: missing or invalid credentials. Check credential type as well as its value.
* **403**: insufficient membership/permissions, disallowed channel or origin.
* **404**: unavailable resource, including a conversation outside a client's scope.
* **409**: a pending message/delivery, conflicting message ID, ownership conflict or Git merge conflict. Follow the operation's retry instructions.
* **422**: deployment validation failed or unsupported transport content.
* **429**: rate/pending-message limit exceeded.

Most application errors use `error.code`, `error.message` and a request ID; some channel routes return plain status text. Retain the `x-request-id` response header when asking for support.