Skip to main content
Each workspace project name has at most one project key. The raw secret is returned only when created or regenerated.

​
Scope: one key per workspace/project name

Keys are selected by authenticated user and exact project_name; Central does not create separate keys.

​
Consumers: Feedback and App Logs

​
Key format and storage model

​
Generate/copy-once behavior

Open Settings → API Key and select Generate Key. Creation initializes both default Feedback schemas. Copy raw_api_key immediately; later reads return only its hint and metadata.

​
Regenerate behavior and preserved configuration

Select Regenerate to replace the secret. The old key stops working; issue schema, feature schema, and feedback rate limit are preserved. The new raw key is shown once. Regeneration allows five requests in the shared limiter window; its duration is not established by this route.

​
Revoke behavior

Select Revoke to delete the key. Feedback and App Logs fail until a new key is created and deployed.

​
Last-used metadata

The UI displays the hint, creation timestamp, and last_used_at when used.

​
Required headers per integration

​
Server-side storage guidance

Keep Feedback’s AIOLA_KEY in a backend/deployment secret; React calls a backend /api/report proxy. App Logs uses NEXT_PUBLIC_AIOLA_KEY, VITE_AIOLA_KEY, or AIOLA_KEY according to runtime.

​
Authenticated key-management API

These routes require Aiola user/session authentication, not the project key.