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. When sending telemetry data to Honeycomb, the API Key determines the data’s destination Team and Environment. Also, any programmatic request sent to Honeycomb must use an API key.

API keys are set at the Environment level, and apply to all datasets in the Environment.

Find API Keys 

Locate your Environment’s API Keys:

  1. In the left navigation bar under the Honeycomb logo, select the Environments banner. A menu appears with Manage Environments and a list of existing Environments. Display of the Honeycomb UI with the selected Environments banner and resulting Environments menu displayed
  2. Select Manage Environments. The next screen displays a list of Environments and details about each Environment. Display of Environments page
  3. In the row of the target Environment, select View API Keys. The next screen lists the API Keys associated with the Environment. Copy the key value in this screen by selecting the copy icon adjacent to the key value.

Manage API Keys 

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

Note: Honeycomb Classic API keys are scoped to all dataset(s) and data in the Classic section. API keys can be created, modified, or deleted only via the UI. Learn more about Honeycomb versus Honeycomb Classic.

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.

Did you find what you were looking for?