> For the complete documentation index, see [llms.txt](https://docs.mclimate.eu/mclimate-lorawan-devices/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mclimate.eu/mclimate-lorawan-devices/integrations/senet.md).
# Senet
## **Connection between Senet and MClimate’s LoRaWAN broker using Webhooks**
{% hint style="info" %}
The guide assumes you have your device registered with the Senet platform and you have access to the Dashboard.
{% endhint %}
### 1. Creating a notifier in Senet
Expand the device settings for your device in the Senet Dashboard
Device settings
Go to the NOTIFICATION TARGET section and select HTTP from the dropdown menu.
Enter the following URL in the text box:
You will need to create two Header Keys (make sure you name them with these exact names):
* m-token
* api-key
Notification Target
Proceed to the next section of the guide to learn how to generate the Header Values. Leave the rest of the settings with their default values.
### 2. Create Enterprise M-token
Go to and create your m-token.
Creating an m-token
Give it a name and copy it over into the m-token header value field in Senet
Copying the token
### 3. Create a Senet API-key
In the Senet Dashboard navigate to the Edit Account Info section.
Account section
Generate/Re-generate a new API Key and copy it over in the api-key header value field in Senet.
Generating the API-Key
Save the device settings in Senet, now that you have both the M-token and the API-Key and you are done.
Your device should now be visible in Enterprise.
---
# 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.mclimate.eu/mclimate-lorawan-devices/integrations/senet.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.
