Installation
Widget ID
One value in, several values out. How your setup changes in version 3, and what to remove.
Earlier versions asked you to configure one value for the assistant and an additional value for each integration you used. All of them were named “secret key”, and the installation instructions asked you to hide them in an environment file (.env).
That naming was misleading. Those values were always published to the browser, because any code running on your website is downloaded by every visitor. Hiding them in an environment file never concealed them and was never what protected your account.
Version 3 corrects this. There is one value, it is called a widget ID, and it is public by design.
Previously
- An assistant key, plus one key per integration
- All labelled “secret key”
- Instructions to hide them in
.env - Reported by security scanners
- Adding an integration meant a code change
Version 3
- One widget ID for everything
- Named for what it is
- No environment file needed
- Nothing for scanners to flag
- Integrations change nothing in your code
Where to find your widget ID
Your widget ID was sent in the email accompanying your installation guide. It is the only value you need, and the same one is used by every installation method. If you ever want it changed, tell us and we will issue a new one.
What to remove once you have upgraded
These values are no longer read by anything and should be deleted from your code and environment files:
| Old value | Why it can go |
|---|---|
The secretKey property and MENNI_SECRET_KEY, including any NEXT_PUBLIC_ or REACT_APP_ variant | Replaced by your widget ID. |
The menniBokunSecretKey property, MENNI_BOKUN_SECRET_KEY and any other per-integration key | Integrations are now resolved on our servers. |
Any comment instructing you to move these into .env | The instruction was incorrect. |
Credentials you gave us for a booking or e-commerce system stay exactly where they are, stored on our side. They were never present in your website and they still are not.