Api tokensProject api tokens
Add a Project API Token
Generate a new project-scoped token for tools and automations.
Goal
Create a token that can only access one project.
What you need
- A project where you can manage API tokens
- A clear purpose and a role for the token, so it gets only the permissions it needs
To create it:
- Open the target project
- Open
API Tokens - Click
VIEW ALL - Click
ADD API TOKEN - Follow the prompts, choose the role, and confirm
Using Devopness MCP
Try these prompts in Devopness MCP:
- "In organization
acme-inc, projectacme-platform, create a project API token with deploy-only permissions." - "In organization
acme-inc, projectacme-platform, add a project API token for the CI pipeline and set its role."
Verify
- A new project API token is created
- You copy and store the token value immediately, because it is shown only once at creation time
- The token has access only to the resources of the selected project
Common issues
- You cannot add a token: confirm your role in the project
- You cannot copy the token later: the token is shown only once, so store it right away
What to do next
- View a Project API Token to review its scope
- Revoke a Project API Token when it is no longer needed