guides

How to Create an API Token in Krea

The Krea Team ·
How to Create an API Token in Krea

Open API mode

Start in the Krea app and open the workspace dropdown in the top-left corner. Choose Krea API to switch from the creative tools into the API workspace.

The Krea workspace dropdown with the Krea API option visible

Go to tokens

API mode opens with the API home page, quick-start code, documentation links, and account usage. Click Create token on the home page, or open API Tokens from the sidebar under Manage.

The Krea API home page with the Create token link and API navigation

Create a new token

On the API Tokens page, click New Token. This opens the key creation dialog. Existing token values are intentionally hidden here because API credentials should not be shared in screenshots, docs, chats, or tickets.

The API Tokens page with existing token identifiers hidden

Name the token

Give the token a name that explains where it will be used, such as production backend, staging app, or local testing. Clear names make it easier to revoke the right key later.

The new token dialog with a tutorial token name filled in

Click Create key. Krea will show the token once after it is created. Copy it immediately, store it in your secrets manager or environment variables, and avoid putting it directly in client-side code.

Quick checklist

  • Use a specific name for the app, script, or environment that will use the token.
  • Copy the token when Krea shows it; you may not be able to view the full value again.
  • Store it in a secure place such as your deployment secrets or local .env file.
  • Revoke the token if it is exposed, unused, or tied to an old project.

Create an API token

Switch to Krea API mode and create a token for your next integration.

Open API Tokens

Frequently asked questions

Can I see the full token again later?
No. Treat the token as something you need to copy when it is first created. If you lose it, create a new token and revoke the old one.
What should I name my API token?
Use a name that identifies the project and environment, such as `website production`, `automation staging`, or `local experiments`.
Should I use an API token in frontend code?
No. Keep API tokens on the server side or in secure automation environments. Do not ship them in public client-side code.
What should I do if a token is leaked?
Revoke it from the API Tokens page and create a replacement token. Then update the affected app or secret store with the new value.