Skip to main content
Where: sidebar Project Management → API Key tab One API key is issued automatically when you create a project. There is one key per project, and you view and regenerate it here.
API Key tab

The API Key tab — the key is masked, with view, copy, and regenerate controls.

​
What is on the screen

The last-used time is not on this screen. Only the creation time is shown. Below that, the screen shows a Keep your API key safe notice — “Do not share your API key anywhere publicly accessible”, “Regenerate immediately if you suspect the key has been exposed”.

​
Regenerating

Selecting Regenerate opens a confirmation dialog. Confirming invalidates the current key immediately and replaces it with a new one, and it cannot be undone. Requests sent with the old key receive 401 OMNI_4005. Because there is only one key per project, there is no window where the new key and the old key are both valid. API calls fail from the moment you regenerate until you finish the rollout, so plan the order before you start.
1

List what needs the new key first

Write down every server, batch job, and CI pipeline that uses this key. Anything you miss becomes an outage the moment you regenerate.
2

Regenerate and copy the new key

Confirming in the dialog switches to the new key immediately. Copy it before you leave the screen.
3

Update your secrets and redeploy

Replace the value in your environment variables or secret manager and redeploy everything. Until this step is done, calls receive 401.
If you suspect the key has been exposed in a public repository, a log, or client-side code, regenerate it immediately. A single leaked key can read and write every profile, document, and analysis result in that project. There is no narrower, read-only key.

​
Handling the key