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

      Integrations

      • Overview
      • Adding Applications
      • Data Formats
      • Payload Formatters
      • Webhooks
      • Storage Integration
      • Integrate with popular IoT platforms
      • Other integrations
        • MQTT Server
        • Pub/Sub
          • MQTT Client
          • NATS Client
          • Message Types
        • Node-RED
        • IFTTT
      • Application Packages
      • Examples

      Message Types

      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 can be configured to publish messages for any of the following events:

      • Downlink ack
      • Downlink failed
      • Downlink nack
      • Downlink queued
      • Downlink sent
      • Join accept
      • Location solved
      • Service data
      • Uplink message

      The Application Server can be configured to subscribe to messages to schedule the following events:

      • Downlink queue push
      • Downlink queue replace

      JSON messages sent or received by the Application Server are defined in Data Formats.

      Enabling event messaging also allows you to manually configure a Sub topic for that event. If no Sub topic is specified, events will be published to the configured Base topic.

      Separate Sub topics should be specified for Downlink queue push and Downlink queue replace in order to use both. Using the Base topic for both simultaneously will cause messages to randomly be scheduled as either Downlink queue push or Downlink queue replace.

      Topics
      ← NATS Client

      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