Skip to main content
API keys are created from the authenticated AI Gen Studio dashboard. Create separate keys for sandbox testing and live processing.

​
Create a key

When creating a key, choose:
FieldDescription
NameHuman-readable name, for example Production catalog import.
EnvironmentSandbox or Live. This cannot be changed after creation.
Expiration dateOptional. Expired keys cannot authenticate.
The full key is displayed only once. Store it immediately in your backend secret manager.

​
Environments

EnvironmentPrefixBehavior
Sandboxaigen_test_Validates API behavior without provider calls or credit usage.
Liveaigen_live_Processes real images and consumes paid API credits.
Use sandbox keys for CI, Postman collections, local integration testing, and webhook receiver development. Use live keys only from trusted backend environments.

​
Lifecycle actions

ActionBehavior
DeactivateDisables the key immediately. Requests fail with api_key_inactive.
ReactivateAllows the key to authenticate again if it is not expired or deleted.
RevokePermanently disables the key. It cannot be reactivated.
DeleteRemoves the key from the active key list and permanently prevents authentication.
ExpireA key with a past expiration date cannot authenticate, even if active.

​
Limits

5 active API keys per account
5 key creations per hour
20 key creations per day
If a production integration needs higher limits, contact support with expected catalog size, peak concurrency, and processing window.

​
Rotation strategy

  1. Create a new key in the same environment.
  2. Deploy the new key to your backend secret store.
  3. Confirm new API requests succeed.
  4. Deactivate the old key.
  5. Revoke or delete the old key after the rollback window expires.
Do not rotate by editing frontend code. API keys should never be present in client bundles.