> For the complete documentation index, see [llms.txt](https://docs.mercuri.cx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mercuri.cx/features/introduction-mercuri-api/how-do-i-add-my-api-token-to-wix-secret-manager.md).

# How do I add my API token to Wix Secret Manager?

1. After creating the token, copy the token from the API Token Management dashboard.
2. Open your **Wix Dashboard** → **Developer Tools** → **Secrets Manager.**

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

3. Click on **Add Secret**, paste your **Mercuri API token** in the *Value* field, and assign a **Secret Name** (for example: `MERCURI_MESSAGING_API_KEY`).\
   \&#xNAN;*<mark style="color:blue;">Keep this name handy, as you will need to use the</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**same Secret Name**</mark> <mark style="color:blue;"></mark><mark style="color:blue;">in your Velo code in the following steps.</mark>*

<figure><img src="/files/Beji8v3S7gNq3ZfjAJHi" alt="" width="519"><figcaption></figcaption></figure>

{% hint style="info" %}
**Why use Secret Manager in WIX?**

**Easy maintenance:** If the token expires or needs rotation, you only need to update it in Secrets Manager. You do not have to modify every Velo code file where the token is used.

\
**Centralized management:** All Velo code actions can access the same token consistently, reducing errors.
{% 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 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.mercuri.cx/features/introduction-mercuri-api/how-do-i-add-my-api-token-to-wix-secret-manager.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.