> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# 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.

> [!TIP]
>
> 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.

![DialNexa Regenerate API Key modal showing the 24 hour expiry option, expire now option, Cancel, and Continue.](https://mintcdn.com/dialnexa/j4YElRgYrHSfuXTP/images/documentation/screenshots/api-key-regeneration-modal.png?fit=max\&auto=format\&n=j4YElRgYrHSfuXTP\&q=85\&s=33f56ba50e1abe4aa3899adfe8d82b02)

## 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

> [accordion] New key was not copied
>
> Create another key and rotate again.

> [accordion] Old system still uses previous key
>
> Use the 24 hour window for controlled migration.

> [accordion] Wrong workspace key
>
> Check organization context before rotating.

> [accordion] Webhook verification broke
>
> Webhook secrets rotate separately from API keys.

## Related Reading

> [card] [API Keys](https://dialnexa.com/docs/api-access/api-keys.md)
>
> Create keys.

> [card] [Webhook Secrets](https://dialnexa.com/docs/api-access/webhook-secrets.md)
>
> Rotate event secrets separately.

> [card] [Troubleshooting](https://dialnexa.com/docs/reference/troubleshooting.md)
>
> Debug auth issues.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.