Skip to content
34Five.ai / Documentation
Open Studio ↗
Documentation

Find an answer

Browse popular starting points

DocumentationSecurity and Access
Security and Access

API Keys

Create, protect, expire, and revoke a credential for an external client.

Studio / MCP v1Reviewed 2026-10-24
Documentation previewDraft content · Staging instructions · Not approved for production
On this pageWho creates a keyStore it onceUse it with a headless clientExpiry and revocationNext steps

Who creates a key #

An owner or administrator can create a key under Security → API Keys. Choose a recognizable label, an allowed role, and an expiry. The key acts at that role and cannot exceed the creator's role.

Store it once #

The full key is shown once. Store it in your client's supported secret store. Do not place it in a chat prompt, screenshot, repository, or shared setup document.

The implemented format is:

text
34f_<rung>_<account>_<keyId>_<secret>

This is a format description, not a usable key. Staging and production credentials are not interchangeable.

Use it with a headless client #

Configure the client's Authorization header through its secret mechanism:

text
Authorization: Bearer <YOUR_STUDIO_API_KEY>

Call 34five_whoami to confirm the workspace and role before another read.

Expiry and revocation #

Expiry is required. Revoke an unused or exposed key from the API Keys screen. A key also stops qualifying when its creator no longer has the necessary active membership and role.

Next steps #

Review Security and Data Handling and Errors, Limits, and Versioning. Production deployment and independent review remain launch requirements.

34Five DocumentationPrivacyContent 2b5e203ea2