> For the complete documentation index, see [llms.txt](https://docs.qubitro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qubitro.com/platform/credentials/webhook-signing-key.md).

# Webhook Signing Key

The Webhook Signing Key is used to securely interact with No-code Data Sources in Qubitro.

### Overview

The **Webhook Signing Key** is used to securely interact with **No-code Data Sources** in Qubitro. It ensures that incoming webhooks originate from trusted sources by allowing signature verification.

This key is available under the **Credentials** tab for both **Personal** and **Organizational** accounts.

{% hint style="info" %}
The **Webhook Signing Key** is automatically assigned to your account and remains active as long as the account exists.
{% endhint %}

<figure><img src="https://3109056034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfQfo4zX1x0hfOimS9E2u%2Fuploads%2FICKnKsBeLaklToVfbrDA%2FCleanShot%202025-03-03%20at%2023.21.59%402x.png?alt=media&amp;token=feee6814-9583-409a-abd6-8e551b0cff9a" alt="" width="563"><figcaption></figcaption></figure>

### Accessing the Webhook Signing Key

To find your **Webhook Signing Key**:

* Navigate to the **Credentials** tab in your Qubitro account.
* Select **Webhook Signing Key** from the list.
* Copy the key to use it.

{% hint style="warning" %}
🔒 **This key cannot be modified or deleted.** It is system-generated and permanently associated with your account.
{% endhint %}


---

# 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.qubitro.com/platform/credentials/webhook-signing-key.md?ask=<question>&goal=<user_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.