Key rotation and revocation

Integration keys are server-side, organization-scoped credentials. Rotate them through Ramon Admin whenever a key's holder changes, a secret may have been exposed, or as part of your ordinary secret-management schedule.

Rotation procedure

1. Create a replacement key in Ramon Admin and store it in your platform secret manager.
2. Deploy the replacement to all server-side workers and plugin settings.
3. Call GET /integrations/v1/context with the replacement to confirm the organization and key metadata.
4. Confirm normal provisioning, lookup, scoring, and deletion operations use it.
5. Revoke the old key in Ramon Admin.

Revocation takes effect for subsequent Integration API authentication. It does not alter browser tracking keys already assigned to provisioned surveys. If a key is exposed in browser code, logs, a ticket, or source control, revoke it immediately and remove the exposure.