We've recently updated the navigation
You can find Pipelines and Test Analytics in their own sections in the new horizontal menu bar at the top of the page.
Managing API Access Tokens
Buildkite API access tokens are issued to individuals not organizations. You can create and edit API access tokens in your personal settings.
On the API Access Audit page, organization admins can view all tokens that have been created with access to their organization data. As well as auditing user tokens and what access they have, you can also remove a token's access to your organization data if required.
When you create a token, select the organizations it grants access to, and for REST APIS the scope of the access. GraphQL tokens cannot be limited by scope.
Note for contributors to public and open-source projects
You need to be a member of the Buildkite organisation to be able to generate and use an API token for it.
REST API scopes are very granular, you can select some or all of the following:
- Read Agents
read_agents- Permission to list and retrieve details of agents
- Modify Agents
write_agents- Permission to create, update and delete agents
- Read Teams
read_teams- Permission to list teams
- Read Artifacts
read_artifacts- Permission to retrieve build artifacts
- Write Artifacts
write_artifacts- Permission to delete build artifacts
- Read Builds
read_builds- Permission to list and retrieve details of builds
- Modify Builds
write_builds- Permission to create new builds
- Read Job Environment Variables
read_job_env- Permission to retrieve job environment variables
- Read Build Logs
read_build_logs- Permission to retrieve
- Write Build Logs
write_build_logs- Permission to delete build logs
- Read Organizations
read_organizations- Permission to list and retrieve details of organizations
- Read Pipelines
read_pipelines- Permission to list and retrieve details of pipelines
- Write Pipelines
write_pipelines- Permission to create, update and delete pipelines
- Read User
read_user- Permission to retrieve basic details of the user
When creating API access tokens, you can also restrict which network address are allowed to use them, using CIDR notation.
Viewing the API Access Audit page requires admin privileges. The page can be found in the Audit section of the Organization Settings sidebar.
All tokens that currently have access to your organization's data will be listed. The table includes the scope of each token, how long ago they were created, and how long since they've been used.
Click through any token to see more detailed information about its scopes and the most recent request.
The list of tokens can be filtered by username, token value, scopes, IP address, or whether the user has admin privileges.
If you have old tokens that should no longer be used, or need to prevent a token from performing further actions, administrators can remove the token's access to organization data.
From the API access audit page, find the token whose access you want to remove. You can search for tokens using usernames, token scopes, full IP addresses, admin privileges, or the value of the token itself.
Click through the token you'd like to remove, then click the 'Remove Organization from Token' button.
Removing access from a token will send a notification email to the token's owner.
Removing access from a token does not delete the token. Token owners can re-add your organization to their token's scope.
access-token REST API endpoint can be used to retrieve or revoke an API access token. See the REST API Access Token page for further information.
No, you can change the scope and description of a token, or revoke it, but you can't view the actual token after creating it
Yes, the token owner can re-add the organization to the token from their API Access Tokens settings page.
Yes. If you need to delete a token entirely, you can use the REST API
access-token endpoint. You will need to know the full token value.
If you own the token, you can revoke your token from the API Access Token page in your Personal Settings.
The token will lose access to the organization data. Any future API requests will no longer successfully authorize.
API Access Tokens are issued for users within a Buildkite organization. They are stored both in the Buildkite database (linked to the user ID) and with the user for which they're issued.
API Access Tokens are associated with a specific user and can only be revoked by that user. Admins of a Buildkite organization can remove a user from an organization, which prevents the user from accessing any organization resources and pipelines, and prevents access using any API Access Token associated with that user.
API Access Tokens have no built-in expiration date. The best practices regarding regular credential rotation recommended by OWASP suggest rotating the tokens at least once a year. In case of a security compromise or breach, it is strongly recommended that the old tokens are invalidated, and new tokens are issued.