> For the complete documentation index, see [llms.txt](https://docs.datacake.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datacake.de/lorawan/lns/netmore-thingpark.md).
# Netmore ThingPark
## Add Devices
When you add a new LoRaWAN Device, please select the ThingPark LNS.
## URL
Please use the following URL to forward sensor data from any Netmore ThingPark or Community LNS.
* URL: **`https://api.datacake.co/integrations/lorawan/actility/`**
{% hint style="info" %}
`https://api.datacake.co/integrations/lorawan/thingpark/` now also works as an alias for the same endpoint — both paths reach the same handler. The existing `/actility/` URL is unchanged and keeps working for existing integrations, so there's nothing to update if you're already forwarding data.
{% endhint %}
You will find the URL also on the platform in the LoRaWAN Settings inside of "Product & Hardware" in the Configuration Tab of your device.
## Configuring Downlinks
{% hint style="warning" %}
The following steps are only required if you wish to send Downlinks from Datacake to the Device. If you only need upstream messages (sensor to platform), you don't need to go through the following steps.
{% endhint %}
Downlinks use the ThingPark DX API. To set up downlinks, you need the following information:
* Hostname of your ThingPark DX API
* A ThingPark DX API Token
or
* Target Profile Identifier (to be configured in your DX API Platform)
* A valid ThingPark login (email & password)
{% hint style="info" %}
If you change the password of the configured user at a later point, the token Datacake stores becomes invalid and the integration has to be configured again. For this reason it is recommended to create an API-only user.
{% endhint %}
On the device's configuration tab, in the LoRaWAN settings, click the "Change" button on the Network Server panel.
Select ThingPark as your Network Server and choose "Add new configuration" if you don't already have an active ThingPark configuration in your workspace.
This will open a form that lets you input your ThingPark's hostname as well as the token. If you don't have a token yet, Datacake provides a tool that lets you create a token. For this, enter the Hostname, Target profile identifier as well as the ThingPark login details and click "Generate Token". This will create a token for the user on ThingPark and populate the upper Token field.
Once the Token field has been populated, click the "Update" button. This will store the configuration and reflect in a "Downlinks configured" status.
### Delete Configurations
If you need to delete a ThingPark configuration from Datacake, you can do so via the Integrations section in the sidebar. In there, you will find a "LoRa Network Servers" tab that lists all configured ThingPark instances in the workspace with an option to delete them.
---
# 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.datacake.de/lorawan/lns/netmore-thingpark.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.
