Skip to main content
Create and manage API keys from Settings → API keys.

​
Creating an API key

We’ll only show the API key token once at creation time, so store it somewhere safe.
API keys can have account-level permissions, team-scoped permissions, or a combination of both. This means teams can manage their own config via the API without risking changes to other teams’ resources. When you create a new API key, you choose which permissions it has. You can only grant permissions that you yourself have. If you only have team-level permissions, you’ll only be able to create keys with team-scoped permissions.

​
Account-level permissions

Account-level permissions apply across your entire organization. These are the same permissions available when creating custom roles, such as creating incidents, managing workflows, or reading catalog data.

​
Team-scoped permissions

Team-scoped permissions restrict what a key can do to resources owned by specific teams.

​
Permissions required

To manage API keys, you need one of: Users with only team-scoped permissions can create, edit, and delete keys within their team, but cannot manage keys belonging to other teams.
Yes. A key can be associated with multiple teams, but it will have the same set of team-scoped permissions across all of them.
Yes. A single key can have account-level permissions (e.g., read catalog data) alongside team-scoped permissions (e.g., manage schedules for a specific team).