Getting started

The Auth Tokens API mints a single-use identity token for an existing end user. Your backend mints the token, your client passes it to the Messaging SDK, and the SDK exchanges it automatically. This page walks through the mint request and the handoff to the SDK.

For the full flow and the security model, see the Auth Tokens API overview.

Before you begin

• An API token, kept on your backend
• The Ada end_user_id of the person to identify. Create end users, or look them up by your own external_id, with the End Users API.

Step 1: Mint an identity token

Call POST /v2/auth/tokens/ from your backend with the end user’s id:

$
curl -X POST https://EXAMPLE.ada.support/api/v2/auth/tokens/ \
>
  -H "Authorization: Bearer YOUR_API_TOKEN" \
>
  -H "Content-Type: application/json" \
>
  -d '{
>
    "end_user_id": "6657912fd012e36f8bdde124"
>
  }'

A successful request returns 201 with the token:

1
{
2
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
3
  "type": "identity",
4
  "expires_in": 900
5
}

Errors

When your client is about to start or reset a chat session, mint a fresh token. Do not mint tokens in advance or cache them.

Step 2: Pass the token to the Messaging SDK

Return only the token value to your client over HTTPS, then pass it to the SDK as identityToken:

1
import { loadAdaMessaging } from "@ada-cx/messaging-sdk";
2
3
const token = await fetchAdaIdentityToken(); // your backend call
4
5
const ada = await loadAdaMessaging({
6
  handle: "EXAMPLE",
7
  identityToken: token,
8
});

The SDK exchanges the token when the end user engages with the chat. The exchange consumes the token, so every session and every device needs a freshly minted token.

Follow the identity tokens getting started guide for exchange failure handling, re-identification through reset(), and a two-device walkthrough.

Each platform documents its identityToken option:

• Web SDK reference
• iOS SDK reference
• Android SDK reference
• React Native SDK reference