Skip to main content

​
What the project API key is for

Each workspace can have its own project key. Aiola uses that key for:
  • Feedback
  • App Logs
  • future project-level integrations that identify a specific app
This key is different from your account login and from provider credentials like GitHub or Stripe.

​
Where to manage it

Open Project Settings → API Key. The controls depend on the active access mode.

​
Hosted mode

In hosted mode, you can:
  • generate a key
  • reveal the newly created raw key once
  • copy it
  • regenerate it
  • revoke it
After generation, Aiola only shows the raw key once. After that, the UI keeps a hint, not the full value. If you regenerate the key, the old key is revoked and your app setup must be updated. If you revoke it, integrations using the key stop working until you generate a new one.

​
Lifetime/BYOD mode

With an active lifetime/BYOD connection profile, this page shows the profile’s Project Key instead of hosted generate, regenerate, and revoke controls. You can reveal or copy the configured key and use Manage Backend to open Central Settings → Backend.

​
Important behavior

Lifetime keeps project keys, Feedback, App Logs, and related hosted data on the configured backend. If a lifetime backend still needs setup, Aiola prompts you to connect it before enabling these features.

​
When you need it

You will usually need a project key before setting up:
  • feedback submission
  • app logs capture
  • any server-side proxy route that sends project-scoped data to Aiola
Keep the raw key server-side whenever possible. Feedback code should proxy through your own API route instead of exposing the key in the browser.