For the latest updates and improvements, see the latest Cloud documentation instead.
API tokens#
The Codacy API tokens allow you to:
Codacy provides two types of API tokens:
-
Account API tokens are defined at the Codacy user account level. Each account API token authorizes access to the same organizations and repositories as the owner of the account.
-
Project API tokens are defined on individual repositories. Each project API token only authorizes access to the corresponding repository.
The sections below provide detailed instructions on how to generate and revoke API tokens.
Warning
Never write API tokens on your configuration files and keep your API tokens well protected, as they grant owner permissions to your projects on Codacy.
We recommend that you set API tokens as environment variables. Check the documentation of your CI/CD platform on how to do this.
Generating and revoking account API tokens#
You can create new account API tokens programmatically using the Codacy API or using the Codacy UI:
-
Open your account, tab Access management.
-
Click the button Create API token under Account API tokens.
Tip
You can create multiple account API tokens. This can be useful to have a more flexible control by revoking only a specific token.
To revoke an account API token, click the "X" next to the token. After this, all applications or services using that token to access the Codacy API will fail to authenticate and will receive the reply {"error":"not found"}
.
Generating and revoking project API tokens#
You can create new project API tokens programmatically using the Codacy API or using the Codacy UI:
-
Open your repository Settings, tab Integrations.
-
Click the button Add integration and add a Project API integration.
-
Click the button Settings on the Project API integration and copy the project API token.
Tip
You can create multiple (up to 100) project API tokens per repository. This can be useful to have a more flexible control by revoking only a specific token.
To revoke a project API token, click the trash can icon for the corresponding Project API integration. After this, all applications or services using that token to access the Codacy API will fail to authenticate and will receive the reply {"error":"not found"}
.
See also#
- Adding coverage to your repository
- Running local analysis
- Client-side tools
- Creating project API tokens programmatically
Share your feedback 📢
Did this page help you?
Thanks for the feedback! Is there anything else you'd like to tell us about this page?
255 characters left
We're sorry to hear that. Please let us know what we can improve:
255 characters left
Alternatively, you can create a more detailed issue on our GitHub repository.
Thanks for helping improve the Codacy documentation.
If you have a question or need help please contact support@codacy.com.