Use one key per integration
Give each production system its own key instead of sharing one credential across workers, applications, and environments. A focused key can be replaced or revoked without forcing unrelated deployments.
Create the replacement before revoking
Generate a new key in the console and save it immediately in the target secret manager. URLMe displays the complete value only when the key is created.
- Create and store the replacement
- Deploy the new secret to the integration
- Confirm successful API activity
- Revoke the old key
Allow a short overlap window
Keep both keys active while the new deployment rolls across every instance. Confirm the replacement key is being used before revoking the old credential. The key list shows recent activity to support that decision.
Respond quickly to suspected exposure
When a key may be compromised, prioritize containment: create a replacement, deploy it, and revoke the exposed key as soon as the critical callers have switched. Review recent link creation and destinations for unexpected activity.