Skip to main content

Managing API Keys in Kadence

Create, edit, regenerate, and delete API keys, and learn key security best practices.

Liza avatar
Written by Liza
Updated this week

Prerequisites

  • You must be a Global Admin in Kadence

  • API access must be enabled (you’ll see Settings → API Keys if available)


Create an API Key

  1. Login to Kadence

  2. Go to Settings

  3. Select API Keys

  4. Click Add API Key

    Add API Key

  5. Enter a name and description (e.g., "Slack integration - read-only")

  6. Click Create API Key

    Create API Key

You'll be redirected to the API Key Details page, where you can view:

  • API key identifier

  • Client secret (used for authentication)

    API Key Information

Use a meaningful name/description to help manage usage and permissions later.


Edit an API Key

  1. Go to Settings → API Keys

  2. Click the key you want to edit from the list

    API Key List

  3. On the API Key Details page, update the name and/or description

  4. Click Update API Key

    Update API Key Details

Only Global Admins can make changes to API key metadata.


Regenerate an API Key Secret

You can regenerate the client secret for an existing API key if needed (e.g., compromised credentials).

This action is irreversible. You must update all systems using the old secret immediately.

To regenerate:

  1. Navigate to Settings → API Keys

  2. Select the key from the list

    View API Keys

  3. Click Regenerate

    Regenerate Client Secret

  4. Confirm the action in the popup modal

    Regenerate Secret Popup

After regenerating:

  • A success message will appear

  • The new secret will be shown in the details view


Delete an API Key

Only delete API keys that are no longer in use.

  1. Go to Settings → API Keys

  2. Click on the key you want to delete

    View API Keys

  3. In the top-right corner, click the kebab menu (three dots)

  4. Select Delete API Key

    Delete API Key

  5. You’ll be redirected back to the API Keys list after successful deletion

Deleting a key immediately disables all integrations using that key.


API Key Security Best Practices

API keys grant full access to your Kadence environment, so treat them like sensitive credentials.

  • Use meaningful names and descriptions for traceability

  • Store keys securely, using tools like password managers

  • Never check keys into public code repositories

  • Rotate keys regularly and revoke unused ones

  • Use separate keys per integration for safer revocation

  • Kadence API keys use OAuth 2.0 Client Credentials Grant

    • Do not use them in public/front-end/mobile apps


Need Help?

For support, reach out to:
📩 [email protected]

Check our service status at:

For more helpful articles see:
📚 Kadence Help Center

Did this answer your question?