Overview
Posts are community discussion entries within groups. Unlike standard content items (videos, articles), posts live in the community feed and support real-time interactions including comments, reactions, pinning, and live streaming.
Post vs Content
Posts are stored as Content records with a ContentGroup association of type "post". The /api/posts endpoints provide a dedicated interface for working with posts that includes reaction data, comment counts, and admin reply tracking — features not available on the generic /api/content endpoints.
Key Features
- Reactions — each post includes aggregated
reactionCountsand the authenticated user'smyReactionsinline - Comment counts — top-level (non-deleted) comment count on each post
- Admin reply tracking —
adminHasRepliedandadminLastReplyfields - Pinning — posts can be pinned to the top of the feed
- Live streaming — posts can be live streams with broadcast data
- Scheduled publishing — posts can have a future
publishedDate - Keywords — posts can be tagged with group-specific keywords
Authentication
All post endpoints require authentication via Bearer token.
Error Handling
| Status Code | Description |
|---|---|
| 400 | Missing or invalid parameters |
| 401 | Unauthorized — authentication required |
| 403 | Forbidden — not a group member or insufficient role |
| 404 | Post not found |
| 500 | Internal server error |