Understanding API Keys | Honeycomb

We use cookies or similar technologies to personalize your online experience & tailor marketing to you. Many of our product features require cookies to function properly.

Read our privacy policy I accept cookies from this site

Understanding API Keys

Honeycomb uses API keys for a number of different purposes. Any programmatic request sent to Honeycomb must use an API key. API keys are set at the team level, and apply to all datasets within the team.

Manage API Keys  🔗

API keys are managed at the team level and found in your Team Settings. API keys can be created, modified, or deleted as necessary. You must be a Team Owner to create and edit API keys.

API Key Permissions  🔗

An API key can have any number of the following permissions:

Best Practices for API Keys  🔗

You should use different API keys for different purposes. For example, the API key used to send data in from your production cluster should be different then the API key used for testing; the key used by your build process to create markers should be different from either of those.

Separating these purposes among different API keys allows you to revoke permissions on one key without affecting the abilities of others. It also minimizes the negative effects if a key leaks or is lost.