Discourse Community Forum API
Discourse open-source community forum REST API for developer communities, support forums, and online communities to manage topics, posts, users, categories, tags, and moderation with self-hosted or cloud-hosted deployment. Enables AI agents to manage topic and post creation for community content automation, handle user registration and trust level management for community access automation, access category and tag management for content organization automation, retrieve search and topic list for community intelligence automation, manage private message and notification for member communication automation, handle moderation queue and flag review for community safety automation, access badge and gamification management for community engagement automation, retrieve user activity and stat tracking for community analytics automation, manage group membership and permissions for community governance automation, and integrate Discourse with SSO providers, GitHub, Google, and enterprise identity systems for end-to-end community platform automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Open source forum. GDPR. API key. US/EU. Post, user, and moderation data.
⚡ Reliability
Best When
A developer community, open-source project, or support team wanting AI agents to automate community forum management, topic moderation, user trust levels, and community analytics through Discourse's mature self-hosted or cloud forum platform.
Avoid When
RATE LIMITING VARIES BY TRUST LEVEL AND USER TYPE: Discourse API rate limits differ by user trust level and admin vs member role; automated operations using low-trust-level API keys encounter stricter rate limits; automated bulk operations using member-level credentials may hit rate limits quickly; use admin API key for automation to avoid trust-level throttling. PLUGIN ECOSYSTEM AFFECTS API ENDPOINTS: Discourse plugins significantly extend platform capabilities and add custom API endpoints; automated integrations depending on plugin-specific endpoints must verify plugin installation; automated workflows assuming standard Discourse endpoints may fail on instances without required plugins. SELF-HOSTED vs CLOUD VERSION DIVERGENCE: Discourse self-hosted instances may run older versions with different API capabilities; automated integrations for Discourse Cloud vs self-hosted must account for version differences; automated API calls using newer endpoints fail silently on older self-hosted instances without clear version error.
Use Cases
- • Managing developer community forums from community automation agents
- • Moderating discussions from content safety agents
- • Creating support knowledge bases from customer success agents
- • Analyzing community health from engagement analytics agents
Not For
- • Real-time chat (use Slack or Discord for real-time messaging)
- • Gated paid communities with subscriptions (use Circle or Mighty Networks)
- • Internal company knowledge wikis (use Confluence or Notion)
Interface
Authentication
Discourse uses API key with username header for authentication. REST API with JSON. San Francisco, California HQ. Founded 2013 by Jeff Atwood, Robin Ward, and Sam Saffron (Stack Overflow co-founders). Open source (AGPL). Products: Community forum, trust system, badges, plugins, Discourse Cloud (hosted). Integrations: SSO, GitHub, Google, Okta, WordPress. GDPR. Serves 20,000+ communities including GitHub, Meta, Mozilla, and Roblox. Competes with Vanilla Forums, Flarum, and Invision Community for community forums.
Pricing
San Francisco CA. Open source. Self-hosted free. Cloud hosting paid. Annual discount available.
Agent Metadata
Known Gotchas
- ⚠ API KEY + USERNAME REQUIRED FOR ALL REQUESTS: Discourse API requires both Api-Key header and Api-Username header; automated requests with only API key return authentication error; automated integration must include both headers; using 'system' as Api-Username with admin key provides full API access without per-user attribution
- ⚠ TRUST LEVEL GATING FOR AUTOMATED POST CREATION: Discourse trust levels (0-4) gate content creation capabilities; automated post creation using new user account may be blocked by trust level restrictions; automated community management should use admin API key to bypass trust level restrictions for legitimate automation
- ⚠ TOPIC vs POST vs REPLY HIERARCHY FOR CONTENT CREATION: Discourse creates topics (threads) and posts (replies); automated content creation must use correct endpoint — createTopic for new threads, createPost for replies; automated reply using createTopic creates orphaned topic instead of thread reply
- ⚠ WEBHOOK EVENT FILTER CONFIGURATION: Discourse webhooks require configuration of which events trigger delivery (post created, topic created, user created, etc.); automated event processing must verify webhook event subscription includes required event types; automated processing may miss events if webhook was configured with incomplete event list
- ⚠ SOFT DELETE vs HARD DELETE FOR MODERATION: Discourse post deletion is soft-delete by default (post hidden, recoverable); automated moderation must distinguish soft-delete from permanent deletion; automated content removal using hard-delete permanently removes post content and may break reply threads referencing deleted post
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Discourse Community Forum API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.