Skip to content
The Things Stack documentation home
Getting Started Concepts Cloud Enterprise Integrations API Hardware
Getting Started Concepts
Cloud Enterprise
Integrations API Hardware
Get The Things Stack

    Recent searches

      Popular pages

      • Getting Started
      • Adding Gateways
      • Adding Devices
      • Payload Formatters
      • Webhooks
      • Authentication

      No results for “”.

      • Check the spelling, or try fewer or more general words.
      • Ask the community on The Things Network Forum
      • Contact support
      ↑↓ to navigate ↵ to open Esc to close

      Concepts

      • Overview
      • Architecture
        • Components
          • Alert Routing Server
          • Application Server
          • Console
          • Device Claiming Server
          • Device Template Converter
          • Gateway Configuration Server
          • Gateway Server
          • Identity Server
          • Join Server
          • Network Operations Center
          • Network Server
          • Packet Broker Agent
          • Tenant Billing Server
        • ID and EUI Constraints
        • Last Activity
      • Features
      • Networking
      • Migrate to The Things Stack
      • Packet Broker
      • Server Addresses
      • Advanced Topics
      • Troubleshooting
      • The Things Stack Sandbox

      Application Server

      Updated 20 January 2025 Edit on GitHub
      Copy page
      • View as MarkdownThis page as plain text
      • Open in ChatGPTAsk questions about this page
      • Open in ClaudeAsk questions about this page

      The Application Server handles the LoRaWAN® application layer, including uplink data decryption and decoding, downlink queuing and downlink data encoding and encryption.

      It hosts an MQTT server for streaming application data, supports HTTP webhooks as well as pub/sub integrations.

      Connectivity

      Applications can connect to Application Server over multiple protocols and mechanisms.

      MQTT Protocol

      Applications can connect to an Application Server by exchanging JSON messages over MQTT. MQTT is available over TLS, providing confidentiality of messages exchanged between applications and the Application Server.

      The upstream messages do not only contain data uplink messages, but also join-accepts and downlink events, on separate topics.

      See Application Server MQTT server for more information.

      HTTP Webhooks

      Applications can get streaming JSON messages via HTTP webhooks, and schedule downlink messages by making an HTTP request to the Application Server.

      Like MQTT, all upstream messages can be configured, including uplink messages, join-accepts and downlink events, each to separate URL paths.

      See HTTP webhooks for more information.

      Pub/Sub Integrations

      Applications can also use pub/sub integrations to work with streaming data. This includes connecting to an external MQTT server and NATS server.

      Message Processing

      The Application Server can decode and encode binary payload sent and received by end devices. This allows for working with structured streaming data, such as JSON objects using MQTT and HTTP webhooks, yet using compact binary data that is transmitted over the air.

      Message processors can be well-known formats or custom scripts, and can be set on the device level, or for the entire application.

      ← Alert Routing Server Console →

      On this page

      • Connectivity
      • Message Processing

      Sections

      Getting Started

      Concepts

      Cloud

      Enterprise

      Integrations

      API

      Hardware

      Sitemap

      View our Sitemap

      Contributing

      GitHub

      About Us

      The Things Industries

      Privacy Policy

      Cookie settings

      Cookie Settings

      We use cookies to enhance your experience, analyze site traffic and deliver personalized content. Read our Privacy Policy.

      Cookie categories