Different mabl API keys are permissioned for different use cases. Keys only have the read/write permissions necessary for a specific use case. See managing API keys for more information on working with API keys in mabl.
| API key type | Use |
|---|---|
| CI/CD Integration | Use with mabl’s CI/CD integrations, including Jenkins, Bamboo, Microsoft Azure DevOps, GitHub Actions, and Octopus Deploy. |
| Command Line Interface | Use with the mabl CLI. |
| Deployment Trigger | Use to start tests with the Deployment Events API and to retrieve test results with the Execution Result API. |
| Editor | Use to perform actions permitted by the editor role. |
| Issue Tracker | Use with the mabl Jira plugin. |
| Link Agent | Use with the mabl Link agent. |
| Java Selenium Agent | Use with Selenium Java Agent. |
| Usage Analytics | Use with the mabl Segment integration. |
| Viewer | Use for mabl API endpoints that are read-only, such as the Reporting API. |
| Workspace admin | Use for read-write permissions with credentials and Link Agents. |
| User management | Use to automate user provisioning and role assignment at the company level. Created from the company dashboard |
The Integration key type is deprecated. Existing legacy Integration keys will continue to function, but users cannot create new API keys of this type.