> For the complete documentation index, see [llms.txt](https://docs.kpnthings.com/kpn-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpnthings.com/kpn-things/getting-started/tutorials/technical-overview/downlink-communication.md).

# Downlink communication

When data is sent to the device

<figure><img src="https://1453626848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl6RrePMSAjRvOgcHjMBZ%2Fuploads%2F4qdoNlGuaaNohVFSeXwY%2Fimage.png?alt=media&amp;token=0116cc12-2e9f-45ef-bb03-8264fbb09c05" alt=""><figcaption></figcaption></figure>

All downlink communication is requested on and managed by the [Actuator API](#actuator-api). Optionally a Destination can request and manage downlink communication as well. See [Destination types](/kpn-things/building-blocks/destinations.md#destination-types) to learn which destinations can support downlink communication.

After a downlink is requested on the Actuator API it is [encoded](#actuator-api). Meaning the downlink is translated to a message the device will understand. After encoding the downlink is send over the selected network to your device.&#x20;

The network (and the device) will report feedback about the delivery of the downlink to the Actuator API. This information can be retrieved by the application, or the Things Connector fetches this information into your system.

## Actuator API

Using the KPN Things Portal, you can request downlinks, and check their progress.&#x20;

Since December 2020 it is also possible to directly call the Actuator API. Head on over to the [API access documentation](/kpn-things/general-functions/apis.md#send-downlink-to-device) for more information!

## Encoder

Using our encoders the downlink request is translated to a device specific message. All available encoders are listed on the Supported devices page.

## Network support

Currently the following networks are supported for downlink communication:

* LoRa downlink
* HTTP response downlink for M2M devices
* HTTP response downlink for Internet-connected devices

## Downlink via Destinations

Some [Destination types ](/kpn-things/building-blocks/destinations.md)also support sending downlinks.


---

# 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.kpnthings.com/kpn-things/getting-started/tutorials/technical-overview/downlink-communication.md?ask=<question>&goal=<user_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.