Skip to main content
Most interactions with Kosli — from the CLI, the API, or CI/CD pipelines — require an API token. This page covers the quickest path to getting one and points to the deeper documentation for each topic.

​
Pick a credential type

Use caseCredentialWhere to manage it
CI/CD, runtime reporters, automationService account API key (recommended)Service accounts
Interactive scripts tied to your userPersonal API keyPersonal API keys
For anything automated, use a service account. Personal API keys inherit your user’s permissions across every organization you belong to, which is rarely what you want for a pipeline.

​
Quick start: get a token

1

Sign in to Kosli

Open the Kosli web app and sign in:
2

Create a key

  • For CI/CD, follow Service accounts to create a service account and generate its first API key.
  • For your own scripts, follow Personal API keys to generate a key tied to your user.
3

Copy the key immediately

Kosli stores only a hash of the token, so the original is shown once and cannot be retrieved later. Paste it straight into your secret store.

​
Use the token

Pass the token as a bearer token when calling the API directly: 
curl -H "Authorization: Bearer <<your-api-key>>" \
  https://app.kosli.com/api/v2/environments/<<your-org-name>>
For CLI usage, basic auth, and full examples, see API authentication methods.

​
See also

Last modified on June 5, 2026