> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/settings/how-to-regenerate-your-api-key-in-doubletick.md).

# How to Regenerate Your API Key in DoubleTick

Your DoubleTick API key allows external applications, CRMs, automation platforms, and custom integrations to securely communicate with your DoubleTick account.

As a security best practice, you may occasionally need to regenerate your API key. This creates a new key and immediately disables the old one, helping protect your integrations from unauthorized access.

{% embed url="<https://youtu.be/C1aON-cuVWU>" %}

#### <mark style="color:$primary;">**Before You Begin**</mark>

Before regenerating an API key, it is important to understand that:

* The existing API key will stop working immediately after regeneration.
* Any application using the old key will stop working until the new key is updated there.
* You should identify all systems using the API key before making changes.

If you are unable to update all integrations immediately, consider creating a new API key instead and gradually migrating your integrations before deleting the old key.

***

#### <mark style="color:$primary;">**Step 1: Open Developer Documentation**</mark>

1. Log in to your DoubleTick dashboard.
2. Click **Settings** from the left navigation menu.
3. Scroll down and select **Developer Documentation**.

This page displays all API keys created within your account.

***

#### <mark style="color:$primary;">**Step 2: Select the API Key**</mark>

1. Locate the API key you want to update.
2. Click on the API key.

A panel will open containing the following tabs:

* Overview
* Usage
* Whitelist

***

#### <mark style="color:$primary;">**Step 3: Review the Usage Tab**</mark>

Before regenerating the key, open the **Usage** tab.

The Usage tab helps you identify:

* Where the API key is currently being used.
* The IP addresses making requests using the key.
* Active integrations connected to DoubleTick.

Review this information carefully so you know which applications or servers will need to be updated after regeneration.

**Tip:** Make a list of all tools, CRMs, automation platforms, and custom applications using the API key before proceeding.

***

#### <mark style="color:$primary;">Step 4: Regenerate the API Key</mark>

1. Return to the **Overview** tab.
2. Click **Regenerate Key**.
3. Confirm the action when prompted.

DoubleTick will instantly generate a new API key.

**Important**

As soon as the new key is generated:

* The previous API key becomes invalid.
* Existing integrations using the old key will stop working.
* You must update the new key in all connected applications.

***

#### <mark style="color:$primary;">**Step 5: Copy and Store the New API Key**</mark>

After regeneration, the new API key will be displayed on the screen.

1. Copy the key immediately.
2. Store it securely in a password manager or another secure location.

You may not be able to view the full key again later, so ensure it is saved before closing the screen.

***

#### <mark style="color:$primary;">**Step 6: Update Your Integrations**</mark>

Replace the old API key with the new one in all connected systems, such as:

* CRM platforms
* Internal applications
* Custom-built software
* Third-party platforms connected to DoubleTick

Once updated, test the integration to confirm it is working correctly.

***

#### <mark style="color:$primary;">**Step 7: Secure the API Key Using IP Whitelisting**</mark>

For additional security:

1. Open the **Whitelist** tab.
2. Enable **Restrict this key to whitelisted IPs**.
3. Enter the public IP address of your trusted server or application.
4. Give the IP a recognizable name.
5. Click **Add IP**.

IP whitelisting ensures that the API key can only be used from approved systems.

Even if someone gains access to the API key, requests from unauthorized IP addresses will be blocked.

***

#### <mark style="color:$primary;">**Alternative: Create a New API Key Instead**</mark>

If you cannot immediately update all integrations, you can create a new API key instead of regenerating the existing one.

This approach allows you to:

1. Keep existing integrations running.
2. Update integrations one by one using the new key.
3. Verify everything is working correctly.
4. Delete the old API key once migration is complete.

This is the safest option for businesses with multiple active integrations.

***

#### <mark style="color:$primary;">**Need Help?**</mark>

<figure><img src="/files/cRrPqmovXubtwKWkZg9W" alt=""><figcaption></figcaption></figure>

If you need assistance regenerating your API key or updating your integrations, click the **Support** button inside your DoubleTick dashboard and our team will be happy to help.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.doubletick.io/settings/how-to-regenerate-your-api-key-in-doubletick.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.