DialNexa API Key Rotation

Rotate DialNexa API keys with immediate expiration or a 24 hour grace period, update external systems, and verify traffic before deleting old access.

DialNexa API key rotation creates a new key and lets users decide what happens to the previous key. When a workspace already has a key, the primary action changes to Regenerate Key and asks whether to expire the previous key now or in 24 hours.

The 24 hour option exists for migrations. The now option exists for confidence or emergencies.

DialNexa API Key Rotation Choices

Pick the option that matches risk.

Choice	Use when
Expire previous key now	The old key is compromised or no system should keep using it.
Expire previous key in 24 hours	You need time to update external systems safely.
Cancel	You are not ready to store and deploy the new key.

The Keys table shows an expiry timestamp for keys in a rotation window. Keys without an expiry timestamp show as active.

Rotate Without Breaking Integrations

1. Choose Regenerate Key

   Pick whether the previous key should expire now or after 24 hours.

2. Create the new key

   Name it by system and date or environment.

3. Store it securely

   Put the raw value in your secret manager while it is visible.

4. Update external systems

   Replace the old key in services, jobs, or apps.

5. Verify calls succeed

   Confirm API traffic works with the new key.

6. Remove old access

   Use immediate expiration or wait for the grace period to end.

Rotation Incidents

New key was not copied

Create another key and rotate again.

Old system still uses previous key

Use the 24 hour window for controlled migration.

Wrong workspace key

Check organization context before rotating.

Webhook verification broke

Webhook secrets rotate separately from API keys.

Related Reading

API Keys

Create keys.

Webhook Secrets

Rotate event secrets separately.

Troubleshooting

Debug auth issues.