DialNexa API Keys

Create and manage DialNexa API keys, including key names, one-time raw key display, expiry status, edit, delete, and regenerate behavior for existing keys.

DialNexa API keys are organization-level credentials used by external systems to access DialNexa APIs. The Keys page lets users create the first key, see the raw key once, copy it immediately, edit key names, see whether each key is active or expiring, delete keys, and regenerate access with controlled expiration for the previous key.

The raw API key is shown once. Copy it into a secret manager before closing the dialog, because the dashboard will not show the same raw value again.

Before You Begin

Know which service will use the key, the minimum permissions it needs, the environment where it will be stored, and who owns rotation and incident response.

API Key Actions

These actions are available from the Keys page.

Action	Behavior
Create first key	Creates a named API key and shows the raw key once.
Regenerate key	Appears when a key already exists. It asks whether to expire the previous key now or in 24 hours before creating the new key.
Copy raw key	Copies the newly created key while the one-time dialog is open.
Edit key name	Changes the label used in the table.
Delete key	Removes the selected key.
Expires	Shows Active for keys without an expiry date, or the exact expiry timestamp for a key in its rotation window.

DialNexa allows up to 2 API keys in the current dashboard flow. If the workspace already has two keys, delete an unused key or wait for an expiring key to clear before creating another one.

Create A Key Safely

1. Open Keys

   Use the workspace where the external system should connect.

2. Choose Add Key or Regenerate Key

   Enter a name that identifies the system or environment.

3. Copy the raw key immediately

   Store it in your secret manager.

4. Close the dialog only after storing

   The raw key will not be shown again.

5. Rotate old keys intentionally

   Use now or 24 hour expiration based on migration risk.

API Key Mistakes

Using a key from another workspace

Keys are organization-scoped.

Naming every key production

Use system and environment names.

Closing before copying

Create a new key and rotate if the raw value was lost.

Sharing in chat

Use a secret manager, not messages or docs.

Verify The API Key

Store the key in a secret manager, make one low-risk authenticated request, and confirm the expected response. Never paste the key into client-side code, screenshots, tickets, or documentation.

Related Reading

Key Rotation

Rotate keys safely.

Webhook Secrets

Manage event verification secrets.

External Webhooks

Configure event receivers.