Qase offers two different types of API tokens to authenticate reporter requests. They are:
Personal tokens
Application tokens
Personal tokens
Personal tokens are used to verify your identity when making API requests to Qase. Before you can perform actions in a workspace via the API, you need to get a token.
Here’s how to create a personal token in Qase:
Go to this link 🔗, or
1. Click on your user profile picture in the Qase app.
2. Choose “API Tokens” from the menu.
3. Click on “Create a new API token”.
4. Enter a name to identify the token for later, and click “Create.”
5. Copy the token that appears on your screen (the token cannot be viewed again once you leave this screen)
An API token has the same permissions as the user who created it in the workspace.
If your user role doesn’t allow you to create test runs, you won’t be able to do that in the Qase interface or through API requests.
App tokens
App Tokens are used for specific integrations with automated testing tools, acting as a crucial part of how these tools connect with Qase.
When an App Token is issued and used, the results, cases, and runs created by the API reporter will appear as being created by the app itself, not by a specific user.
Each API reporter app that can integrate with Qase has its own access token that you can create. For example, here’s how to generate an access token for Playwright:
