Skip to content

docs: document dashboard-issued iams_live API keys - #26

Merged
Si40Code merged 1 commit into
mainfrom
agent/document-iams-api-keys
Aug 11, 2026
Merged

docs: document dashboard-issued iams_live API keys#26
Si40Code merged 1 commit into
mainfrom
agent/document-iams-api-keys

Conversation

@Si40Code

Copy link
Copy Markdown
Collaborator

What changed

  • document Dashboard self-service API key creation and management
  • identify production Developer API keys as iams_live_
  • clarify that SDKs send the complete key directly as a Bearer credential, with no client-side token exchange
  • replace obsolete calle_test_key placeholders in Authentication and Quickstart
  • add the August 11 authentication update to What's New

Why

The public guides still described a separate CALL-E-provisioned Developer API credential. Production uses the Dashboard-issued IAMS AccessKey directly, so the old wording caused developers to request or construct unsupported calle_live_ / calle_test_ credentials.

Impact

Developers can copy the complete Dashboard-issued key into CALLE_API_KEY and use the existing TypeScript or Python SDK configuration unchanged. The HTTP and OpenAPI contract remains standard Bearer authentication.

Production verification

A production probe on August 11, 2026 confirmed that an iams_live_-shaped credential reaches IAMS validation while a calle_live_-shaped credential is rejected by the prefix gate.

Validation

  • pnpm run validate
  • TypeScript typecheck and static build passed
  • 11 OSS deployment tests passed
  • 16 Playwright documentation tests passed
  • git diff --check passed

@Si40Code
Si40Code marked this pull request as ready for review August 11, 2026 03:41
@Si40Code
Si40Code merged commit f2d81cc into main Aug 11, 2026
1 check passed
@Si40Code
Si40Code deleted the agent/document-iams-api-keys branch August 11, 2026 03:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant