From 570cb41193547e19e6b593c43b313076137d5bcc Mon Sep 17 00:00:00 2001 From: "J.Jason" <130959319+JJasonSun@users.noreply.github.com> Date: Tue, 15 Sep 2026 17:02:55 +0800 Subject: [PATCH 1/2] docs: use explicit API key placeholders --- content/guides/authentication.mdx | 7 ++++--- content/guides/changelog.mdx | 2 +- content/guides/quickstart.mdx | 6 ++++-- 3 files changed, 9 insertions(+), 6 deletions(-) diff --git a/content/guides/authentication.mdx b/content/guides/authentication.mdx index 6310e56..c6a670d 100644 --- a/content/guides/authentication.mdx +++ b/content/guides/authentication.mdx @@ -8,13 +8,14 @@ CALL-E uses project API keys for server-to-server requests. ## API keys Create and manage API keys in the [CALL-E dashboard](https://dashboard.heycall-e.com/account/api-keys). -Production API keys use the `iams_live_` prefix. Pass the complete dashboard value directly to the SDK; no client-side token exchange is required. -Store the key in your backend secret manager or runtime environment: +Store the key in your backend secret manager or runtime environment. Replace +`` below with the complete key from the dashboard; the +placeholder is not a working credential: ```bash -export CALLE_API_KEY="iams_live_example" +export CALLE_API_KEY="" ``` Do not commit API keys, print them in logs, send them to browser code, or store them in mobile apps. The CALL-E SDKs are server SDKs for trusted backend services and workers. diff --git a/content/guides/changelog.mdx b/content/guides/changelog.mdx index c61b8e0..39c5bf8 100644 --- a/content/guides/changelog.mdx +++ b/content/guides/changelog.mdx @@ -125,7 +125,7 @@ now reflect confirmed results and preserve a task's true completion state. ## August 11, 2026 -**Dashboard-issued API keys:** Developer API authentication now accepts the `iams_live_` API keys shown in +**Dashboard-issued API keys:** Developer API authentication now accepts API keys issued through the CALL-E dashboard. The server SDK configuration remains unchanged: pass the key through `CALLE_API_KEY`, and the SDK sends it as a Bearer credential. diff --git a/content/guides/quickstart.mdx b/content/guides/quickstart.mdx index 1888732..c5fdcb5 100644 --- a/content/guides/quickstart.mdx +++ b/content/guides/quickstart.mdx @@ -24,10 +24,12 @@ pnpm add @call-e/calle pip install calle-ai ``` -Set your API key before running the examples: +Set your API key before running the examples. Replace `` +with the complete key from the dashboard; the placeholder is not a working +credential: ```bash -export CALLE_API_KEY="iams_live_example" +export CALLE_API_KEY="" ``` You can view your API keys in the [CALL-E dashboard](https://dashboard.heycall-e.com/account/api-keys). From 0f644bfaa3af4a2683fccf2b01ef0167c7ccb40d Mon Sep 17 00:00:00 2001 From: "J.Jason" <130959319+JJasonSun@users.noreply.github.com> Date: Tue, 15 Sep 2026 17:06:06 +0800 Subject: [PATCH 2/2] docs: retain production API key prefix guidance --- content/guides/authentication.mdx | 1 + content/guides/changelog.mdx | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/content/guides/authentication.mdx b/content/guides/authentication.mdx index c6a670d..0eb607a 100644 --- a/content/guides/authentication.mdx +++ b/content/guides/authentication.mdx @@ -8,6 +8,7 @@ CALL-E uses project API keys for server-to-server requests. ## API keys Create and manage API keys in the [CALL-E dashboard](https://dashboard.heycall-e.com/account/api-keys). +Production API keys use the `iams_live_` prefix. Pass the complete dashboard value directly to the SDK; no client-side token exchange is required. Store the key in your backend secret manager or runtime environment. Replace diff --git a/content/guides/changelog.mdx b/content/guides/changelog.mdx index 39c5bf8..c61b8e0 100644 --- a/content/guides/changelog.mdx +++ b/content/guides/changelog.mdx @@ -125,7 +125,7 @@ now reflect confirmed results and preserve a task's true completion state. ## August 11, 2026 -**Dashboard-issued API keys:** Developer API authentication now accepts API keys issued through +**Dashboard-issued API keys:** Developer API authentication now accepts the `iams_live_` API keys shown in the CALL-E dashboard. The server SDK configuration remains unchanged: pass the key through `CALLE_API_KEY`, and the SDK sends it as a Bearer credential.