Client Tokens

A client token lets the browser call Channel3 without your API key. It looks like c3_ct_…. It can only run turns and read the one conversation it is bound to. The API key that minted it pays for those turns. Mint on your server. Never mint from the browser. Send the token as Authorization: Bearer c3_ct_… — see the quickstart.

Mint

Default lifetime is 30 minutes (ttl_seconds from 60 to 7200).

const created = await server.conversations.clientTokens.create();
// created.token        — c3_ct_…
// created.token_id
// created.expires_at

created = server.conversations.client_tokens.create()
# created.token, created.token_id, created.expires_at

curl -X POST https://api.trychannel3.com/v1/conversations/client_tokens \
  -H "x-api-key: $CHANNEL3_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

With no conversation_id, the token’s first turn creates the conversation and the token is bound to it. That is the quickstart path.

Pin a token to an existing conversation

Pass conversation_id when the shopper already has a chat — for example they refreshed the page and you minted a new token. The token can only continue and read that conversation. Any other id returns 404.

const scoped = await server.conversations.clientTokens.create({
  conversation_id: conversationId,
  ttl_seconds: 600, // optional, seconds
});

scoped = server.conversations.client_tokens.create(
    conversation_id=conversation_id,
    ttl_seconds=600,
)

curl -X POST https://api.trychannel3.com/v1/conversations/client_tokens \
  -H "x-api-key: $CHANNEL3_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"conversation_id": "conv_123", "ttl_seconds": 600}'

An expired or revoked token returns 401. Mint a new one before it expires. If you already have a conversation_id, pass it so the new token stays on the same conversation.

Revoke

Revoke from the server when the session ends. Put the token in the body so it stays out of URL logs.

await server.conversations.clientTokens.revoke({ token: "c3_ct_..." });

server.conversations.client_tokens.revoke(token="c3_ct_...")

curl -X POST https://api.trychannel3.com/v1/conversations/client_tokens/revoke \
  -H "x-api-key: $CHANNEL3_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"token": "c3_ct_..."}'

⌘I

Getting Started

Make a Search

Get Product Data

Conversational Agent

Checkout

Pricing, Reporting, and Commissions

Build

Integrate

FAQ

Mint

Pin a token to an existing conversation

Revoke

​Mint

​Pin a token to an existing conversation

​Revoke

Mint

Pin a token to an existing conversation

Revoke