Skip to main content
Gloo AI Studio is where you create and manage the API keys that authenticate you with the Gloo AI API.
Make sure your organization can create keys. Creating an API key requires credit in your organization’s wallet: a balance above zero, or promotional credit. Until then, the API Keys page sends you to the Billing page. Only organization Admins can add credits, so if you are not one, ask an Admin to fund the organization’s prepaid credits, then come back. See Prepaid Credits.Know the permissions. Any member of your organization can create an API key. A key can be deleted by the person who created it or by an organization Admin. If you need someone else’s key removed, ask an org admin.Gloo Code doesn’t use the keys on this page, so organizations that only use Gloo Code don’t see API Keys. You sign in to it from the browser, and it manages its own credential for you — nothing to create, copy, or paste. See the Gloo Code installation guide.

Generating an API Key

1

Navigate to API Keys

In the Studio sidebar, click “API Keys”.
2

Create the key

Click “Create New Key”, enter a name and click “Create Key”. Studio generates a new API key.
Treat your API key like a password! It will only be shown once — copy it immediately and store it in a secure location. After creation, only the obfuscated value (e.g., sk_...3456) is displayed in Studio.
3

Use the key in API calls

Send it directly as a bearer token in the Authorization header:

Key Status and Deleting Keys

Each key in the table has a Status: To remove a key, use the Delete action on its row. Only the key’s owner or an organization Admin can do this. A deleted key stops working shortly afterwards. Delete any key that is compromised or no longer used, then create a replacement and update your applications.

Legacy Client ID and Secret credentials

Legacy: Client ID / Client Secret credentials are deprecated and will be sunset by December 2026. They continue to work until then and are listed on the separate legacy API Credentials tab of this page. To migrate, create a new API key above and update your applications to use it directly (no token exchange needed). See Legacy: client credentials and OAuth for details.

Next steps

Keep each key on your server and out of source control, and replace one that may be exposed: see API Key Security.

Developer Quickstart

Make your first API call with your key.

Chat Playground

Test models before writing code.

Authentication tutorial

Use your key in API calls.