> For the complete documentation index, see [llms.txt](https://docs.darkbot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.darkbot.io/credentials-page/credentials-details-page/interacting-with-connected-exchange-options-and-features/how-to-edit-api-keys-for-connected-exchange.md).

# How to edit API Keys for connected Exchange

Editing API keys for connected exchanges is essential when the existing keys have expired or when users want to update them for various reasons. By following a few simple steps, you can easily update your API keys and ensure seamless trading operations. This guide will walk you through the process:

**1. Access the Credentials Details Page** 

To begin the API key editing process, navigate to the [Credentials details page](/credentials-page/credentials-details-page/how-to-go-to-the-credentials-details-page.md).

**2. Locate the API Key & Secret Widget** 

On the Credentials Details page, locate the API Key & Secret widget. This widget provides a convenient interface to manage and update your API keys. It is on the left side of the page at the bottom.

<figure><img src="/files/z1bWIKS5bMNh2zHuwPO4" alt="API Keys &#x26; Secret widget"><figcaption><p>API Keys &#x26; Secret widget</p></figcaption></figure>

**3. Access the API Key Settings**&#x20;

Within the API Key & Secret widget, click on the gear icon located in the top right corner. This will open a pop-up window where you can enter the new API key and secret key.

<figure><img src="/files/I16jWiMcqVT5q7ruuVDY" alt="Edit credentials button"><figcaption><p>Edit credentials button</p></figcaption></figure>

**4. Enter the New API Key & Secret Key**&#x20;

In the pop-up window, enter the new API key and secret key in the designated input fields. Make sure to obtain the updated API keys from the exchange platform.

<figure><img src="/files/TSpeXlxBMUQcQduBoaGQ" alt="Edit credentials settings popup"><figcaption><p>Edit credentials settings popup</p></figcaption></figure>

**5. Save the Changes**&#x20;

After entering the new API key and secret key, click the \[Save] button to save the updated credentials.

<figure><img src="/files/1IbKxY4qqlGYx73NYM0c" alt="Save changes button"><figcaption><p>Save changes button</p></figcaption></figure>

**6. Wait for the Confirmation Notification**&#x20;

Once you have saved the changes, wait for the notification confirming the successful update of your API keys. This notification ensures that the new keys have been applied and are ready for use.

<figure><img src="/files/ZAbBvz8zopCCF1uI3ndZ" alt="Notification of a successful change of settings"><figcaption><p>Notification of a successful change of settings</p></figcaption></figure>

**Conclusion:**&#x20;

Updating API keys for connected exchanges is a crucial task for maintaining secure and uninterrupted trading activities. By following the steps outlined in this guide, you can easily edit your API keys and ensure the smooth functioning of your trading operations. Remember to always keep your API keys secure and regularly update them as needed.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.darkbot.io/credentials-page/credentials-details-page/interacting-with-connected-exchange-options-and-features/how-to-edit-api-keys-for-connected-exchange.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.