--- title: Discourse API Integration on Truto slug: discourse category: Knowledge Management canonical: "https://truto.one/integrations/detail/discourse/" --- # Discourse API Integration on Truto **Category:** Knowledge Management **Status:** Generally available ## Unified APIs ### Unified Knowledge Base API - **Collections** — - **Comments** — - **Page-Content** — Represents the content of a page - **Pages** — Represents the pages, posts, articles in a knowledge base - **Tags** — Represents the tags in a knowledge base ## How it works 1. **Link your customer's Discourse account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Discourse.** The Proxy API is a 1-to-1 mapping of the Discourse API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Ingest community knowledge for AI-powered support deflection** — AI customer service platforms can connect to their customers' Discourse instances to pull topics, replies, and accepted answers across categories — building a rich knowledge source for RAG pipelines that deflect support tickets with community-verified answers. - **Track community signals for account health scoring** — CRM and revenue intelligence platforms can sync Discourse topics and comments to detect churn signals (frustrated bug reports from key accounts) or upsell opportunities (high engagement from enterprise users), all without building bespoke Discourse API integrations. - **Unify community threads into a helpdesk agent workspace** — Helpdesk SaaS products can pull Discourse topics from specific categories into their ticketing UI and push agent replies back as comments, letting support teams manage community conversations alongside traditional tickets from a single queue. - **Surface community discussions inside documentation portals** — Developer documentation platforms can fetch Discourse topics by tag to display relevant community Q&A, workarounds, and code snippets alongside static API docs — blending curated content with living community knowledge. - **Automate content categorization and tagging workflows** — Content operations platforms can read new Discourse topics, run external classification or sentiment analysis, and apply tags programmatically — enabling automated moderation and content routing at scale across customer communities. ## What you can build - **Community knowledge ingestion pipeline** — Pull all topics (Pages), their body content (Page-Content), and threaded replies (Comments) organized by category (Collections) to feed search indexes or AI models. - **Category-scoped content sync** — Let end users select specific Discourse categories like 'Support' or 'Feature Requests' as Collections, then continuously sync only relevant topics and comments into your product. - **Tag-based content discovery** — Query Discourse topics by Tags to surface contextually relevant community threads inside your product — such as showing all discussions tagged with a specific API endpoint or feature name. - **Bi-directional comment threading** — Read Comments from Discourse topics into your app and push new replies back as Comments, enabling agents or users to participate in community discussions without leaving your product. - **Cross-instance community aggregator** — Connect multiple customers' Discourse instances through a single Unified Knowledge Base API, normalizing categories, topics, and tags into a consistent schema regardless of each instance's configuration. - **Community-to-ticket escalation workflow** — Monitor new Pages in specific Collections for unresolved questions, automatically create internal tickets, and sync resolution status back by updating the Discourse topic. ## FAQs ### How does authentication work for Discourse integrations through Truto? Discourse supports API key-based authentication. Admins can generate global API keys or per-user keys from the Discourse admin panel. Truto handles storing and managing these credentials so your end users authenticate once through the Truto Connect flow. ### How does Discourse map to Truto's Unified Knowledge Base API? Discourse Categories map to Collections, Topics map to Pages, the original post body maps to Page-Content, replies map to Comments, and Discourse's tagging system maps to Tags. This gives you a normalized schema to read and interact with Discourse content. ### Are there rate limits on the Discourse API? Yes. Discourse enforces per-user and global rate limits, typically 60 requests per minute for user-scoped keys and 200 requests per minute for global keys. Truto handles pagination and can manage request throttling so you don't need to build retry logic yourself. ### Can I filter Discourse topics by category or tag? Yes. Discourse's API supports filtering topics by category (Collection) and by tag (Tags), so you can scope data ingestion to only the content your product needs rather than pulling the entire forum. ### Is the Discourse integration available out of the box on Truto? Discourse is supported through Truto's Unified Knowledge Base API with resources for Collections, Pages, Page-Content, Comments, and Tags. Custom tools and additional endpoints can be built on request to match your specific workflow needs. ### Does this integration support both reading and writing data? Discourse's API is fully bidirectional — every action in the Discourse UI has a corresponding API endpoint. Through the Unified Knowledge Base API, you can read topics, comments, and categories as well as create new content and replies, subject to the permissions of the authenticated API key.