The Notification Server API provides a unified interface for managing and delivering notifications across the Hoody platform. It handles the routing, delivery, and lifecycle of notifications, ensuring that messages reach their intended recipients reliably and in real time.

This overview introduces the core concepts and capabilities of the Notification Server. Use it as a starting point to understand how notifications are structured, how delivery channels are managed, and how the system handles retries, acknowledgments, and user preferences.

The Notification Server is designed to support:

• Multi-channel delivery — Send notifications across push, email, and in-app channels from a single API surface.
• Asynchronous processing — All delivery operations are non-blocking, returning immediately while notifications are processed in the background.
• Retry and failure handling — Built-in retry logic with configurable backoff ensures transient failures do not result in lost notifications.
• User preference management — Respect per-user notification settings, including channel opt-outs, quiet hours, and priority filtering.
• Delivery tracking — Query the status of any notification, including pending, delivered, and failed states, with detailed failure reasons.

The endpoints in this section cover the full notification lifecycle: creating and dispatching notifications, managing templates, configuring channels, and inspecting delivery status. Whether you are integrating notifications into a new application or extending an existing integration, these endpoints provide everything needed to build a reliable notification experience on Hoody.

Refer to the individual endpoint pages in this section for detailed request and response specifications, authentication requirements, and SDK examples.