> For the complete documentation index, see [llms.txt](https://docs.korewireless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.korewireless.com/kore/developers/how-to/webhooks/rotate-my-webhook-secret.md).
# Rotate my Webhook Secret
KORE signs every event it sends with the current `Active` secret key, which there is only ever one of. Rotating a secret allows you to invalidate your old one and have KORE use a new one to sign. You may want to do this because you lost your old secret or your old secret was compromised.
If you wish to rotate your secret, you can create a new secret and mark it as `Active`.
First, navigate to the **Webhook** dashboard and click **Create** to create a new secret.
This will create a secret with `Pending` status.
{% hint style="info" %}
The first secret you create will be created in an `Active` state.
Any new secret created afterwards will be`Pending`, which you can mark as `Active` when ready.
Any additional secrets created will overwrite the previous `Pending` secret, if one exists.
{% endhint %}
To rotate the current `Active` secret, click on the **Activate** button. This will disable the current `Active` secret and mark the `Pending` secret as `Active`.
{% hint style="danger" %}
**Rotating a secret cannot be undone.**
When rotating, ensure you are prepared to receive the new `Active` secret in your implementation. Otherwise, all validations will begin to fail, as KORE will no longer be using old secrets.
{% endhint %}
Rotate the secret
Pending became active
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.korewireless.com/kore/developers/how-to/webhooks/rotate-my-webhook-secret.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
