# Integrations

### Integrate your LoRaWAN Network Server (LNS) Account

Akenza seamlessly integrates with various connectivity providers. These integrations can be used to **connect**, **synchronize** and **manage** Assets of a connectivity provider account.

![Integrations](/files/s0RPAVTcR5mci5U1u26z)

The below list consists of all supported connectivity providers and their feature sets.

<table data-header-hidden><thead><tr><th>Integration provider</th><th width="150">Type</th><th>Coverage</th><th width="150">Asset Sync</th><th>Data Routes</th></tr></thead><tbody><tr><td><strong>Integration provider</strong></td><td><strong>Type</strong></td><td><strong>Coverage</strong></td><td><strong>Asset Sync</strong></td><td><strong>Data Routes</strong></td></tr><tr><td>Swisscom LoRaWAN</td><td>LoRaWAN</td><td>Switzerland</td><td>Yes</td><td>Yes</td></tr><tr><td>EWZ LoRaWAN</td><td>LoRaWAN</td><td>Zurich</td><td>Yes</td><td>Yes</td></tr><tr><td>Loriot</td><td>LoRaWAN</td><td>global</td><td>Yes</td><td>Yes</td></tr><tr><td>Actility's ThingPark Wireless</td><td>LoRaWAN</td><td>global</td><td>Yes</td><td>Yes</td></tr><tr><td>The Things Network</td><td>LoRaWAN</td><td>global</td><td>Yes</td><td>No</td></tr></tbody></table>

Integrations allow the management of **Devices** and **Sim Cards** of connectivity providers. This enables the integration of already existing assets into akenza and manages all **Assets** from a single point.

Depending on the connectivity provider, multiple options for authorizing the process are available. These are described in the individual documentation.

### Synchronizing an Integration

By clicking on the synchronize action on the Integration list, the synchronization process starts.\
On the first setup, the Integration synchronizes automatically. All changes will be applied from the connectivity provider to the **Inventory** list of akenza. New devices will be created, updates will be reflected and deleted devices will also be deleted on akenza.

If a device gets created or updated in akenza, and is linked to integration, these changes will also be reflected on the platform of the connectivity provider. Deleting devices will be reflected as well. Therefore no double-handling on the integration account is required.

By adding an **Integration**, an appropriate device connector will be created simultaneously. This new **Device Connector** can be used in **Data Flows** to receive and process data from  IoT devices in akenza.

### Data Routes

Data Routes reflect the data output of the connectivity provider platform. This can either be akenza or any other third-party provider.\
Depending on the connectivity provider, Data routes can be created and managed through akenza.&#x20;

In order to create a new **Data Route**, the button in the top right corner needs to be clicked. The Integration to create the data route has to be selected, as well as all properties for the data route specified.

Existing data routes can be deleted by selecting the + (plus) icon on the Integration list and clicking the delete action in the appropriate data route entry.&#x20;

{% hint style="warning" %}
It is not possible to create **Data Routes** or synchronize **Devices** or **Sim Cards** using out-of-the-box connectivities.\
Their **Device Connectors** however can be used in **Data Flows** which allows creating **Devices** and receiving and processing their data in akenza.

Deleting an **Organization** which contains **Assets** managed through CaaS will also be irreversibly deleted on the connectivity provider platform.
{% endhint %}

### Device Connectors

When creating an integration, a device connector will be created. It can be used to receive and process data from your IoT assets in akenza.


---

# Agent Instructions: 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:

```
GET https://docs.akenza.io/akenza.io/get-started/integrations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.