# Loriot

{% hint style="success" %}
Loriot provides a global Low Power Network (LPN) over LoRaWAN. The use of the community server is offered for free. For a private LoRa network, the own server can be purchased.
{% endhint %}

On akenza, two options are available to make use of the **Loriot LoRaWAN network**:

1. [Connectivity-as-a-Service](#connectivity-as-a-service)
2. [Connecting own account](#connecting-own-account)

### 1. Connectivity-as-a-Service

The **Loriot LoRaWAN network** can be chosen on akenza as [Connectivity-as-a-Service](https://akenza.io/features/connectivity-as-a-service) (CaaS). Therefore, *Loriot CaaS* needs to be selected on a [Data Flow](/akenza.io/get-started/your-data-flow.md) as [device connector](#device-connectors). 

{% hint style="success" %}
CaaS allows one to quickly get started with an IoT project without the need of setting up an individual account for a network provider. The LoRaWAN account gets managed through akenza. Device connectivity prices will be invoiced automatically through akenza. **No connectivity costs** will occur by using the Loriot Network.
{% endhint %}

### 2. Connecting own account

The seamless integration from the LoRa network into akenza makes the management of already connected IoT devices and new projects effortless. 

Two authentication methods to set up the integration are provided:

* Username and password
* API key (to be created in *Account - API keys* of Loriot)

When authenticating with a username and password, akenza creates an API key on the Loriot server which is used for further communication.\
When authenticating with an API key, the key is stored encrypted in akenza and used for further communication with the Loriot system.

{% hint style="warning" %}
The username and password are not stored in akenza.
{% endhint %}

The appropriate host can be selected or if applicable, the URL has to be entered from the own Loriot server. Furthermore, the preferred authentication method can be chosen. 

![Loriot integration setup](/files/buSZyjqiInDjqA5c0j74)

After the credentials have been verified, the integration name can be introduced and the application on the Loriot server selected. A new application can be created, or in the case of an already existing IoT project, there is the option to directly connect to the existing one.

In the case of a new application, a name and the specification of the maximal device capacity of the application are given. Whether or not to process the data in akenza and/or send it to a 3rd party system instead, can also be specified.

If processing the data in akenza is chosen, each device created through akenza will forward its data to akenza. 

If the data shall be processed in a different way, the data routing can be set in the Loriot account.

When creating a new data route, the destination URL and authorization header need to be set.\
Noting that the authorization header will be in the following format:

```
curl -H "Authorization: <the field value>" https://<the-url>
```

{% hint style="info" %}
Other custom headers can't be added.
{% endhint %}

![Account details of integration setup](/files/TbnzWXElgbQAJc5hjcpZ)

After the setup, the integration gets created and the initial synchronization will start. Depending on how many devices are registered, the process can take a few minutes.

Once the synchronization succeeds, all devices will be displayed in the overview of the tab *Assets*. The devices can now be managed on akenza.&#x20;


---

# 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/your-data-flow/device-connector/lorawan/loriot.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.