Organization-owned API key
Each active Platform organization has one active production key. Authentication resolves requests to that organization before public production access is allowed.
This page states only behavior that is part of the current Ruwana Platform contract. It does not substitute marketing claims for controls that have not been published as a contract.
Each active Platform organization has one active production key. Authentication resolves requests to that organization before public production access is allowed.
The complete live key is revealed immediately after create or regenerate. Later Platform views expose safe masked key metadata rather than redisplaying the full secret.
Regenerating the organization key replaces the previous production secret, so integrations should update their server-side secret store as one controlled rotation.
Platform-generated media is retained for a fixed seven-day window from original completion. Successful responses expose expiresAt and clientStorageRequired: true.
Use the returned media URL to retrieve the generated result and copy anything that must live beyond the delivery window into your own storage.
Expired media URLs are removed from delivery while request, usage and billing records remain available as non-media history. Idempotent replay does not extend the original media deadline.
RUWANA_API_KEY in server-side secrets or environment configurationplatform.ruwana.studioUse Authentication for key mechanics and Media retention for the exact seven-day response fields.