Skip to main content
DialNexa webhook secrets are organization-level credentials used by receiving systems to verify webhook events. The Keys page lets users create a webhook secret, copy the raw secret, show or hide it in the table, edit its name, delete it, and rotate it with a clear warning.
Rotating a webhook secret can permanently replace the existing secret. Update receivers before they start rejecting valid events.

Webhook Secret Actions

Webhook secrets share the Keys page but serve a different purpose from API keys.
ActionBehavior
Create secretCreates a named webhook secret and shows the raw secret.
Rotate secretWarns that creating a new one will permanently delete the existing one.
Show or hideToggles whether the secret value is visible in the table.
CopyCopies the secret value.
Edit nameChanges the visible label.
DeleteRemoves the webhook secret.

Rotate A Webhook Secret Safely

1

Open Keys

Use the correct workspace.
2

Choose Add Key then Webhook Secret

If one exists, read the rotation warning.
3

Create and copy the new secret

Store it in the receiving system.
4

Update verification logic

Deploy the receiver with the new secret.
5

Send a test event

Place a test call and confirm the receiver accepts it.

Webhook Secret Questions

No. API keys authenticate requests to DialNexa. Webhook secrets verify events sent from DialNexa.
An external webhook can depend on a configured secret. Check the Webhooks page status.
Plan as if rotated secrets cannot be recovered from the dashboard.

External Webhooks

Configure event URL.

Webhook Failures

Debug delivery.

Agent Webhooks

Enable events for agents.