Topic

6.2 APIs

The APIs section documents how Praisma Hub exposes functionality and data to external systems in a controlled and consistent manner. It introduces the philosophy behind public and internal APIs, emphasizing stability, versioning, and security over ad-hoc access.

By covering content delivery, scheduling endpoints, and notification triggers, this topic provides developers with a mental model for how different parts of the platform communicate beyond the UI. It also sets expectations around authentication, rate limiting, and contract-based integration.

Article

6.2.1 Developer Guide — APIs — CMS Public API — Content Delivery

This section explains how the CMS Public API exposes content for delivery, focusing on read-only access, filtering, localization, and safe consumption without coupling clients to internal models.

Article

6.2.2 Developer Guide — APIs — Planner API — Scheduling Endpoints

This section explains how the Planner API exposes scheduling capabilities, focusing on deterministic execution, time-based triggers, and safe automation without coupling clients to internal schedulers.

Article

6.2.3 Developer Guide — APIs — Notification API — Event Triggers

This section explains how the Notification API exposes event-triggered notification creation, focusing on explicit triggers, deterministic delivery, and safe integration without duplicating delivery channel logic.