Discourse API Documentation

Name: Discourse API Documentation API
Brand: Discourse API Documentation
Availability: InStock

✓ Official Vendor SpecCommunicationsChat MessagingapiKey93 EndpointsREST

For Agents

Create topics, post replies, manage users and groups, and run admin operations on a Discourse forum. Useful for community-management, support, and event-coordination agents.

Install Jentic One Beta

Connect the Discourse API Documentation to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Discourse API Documentation, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Discourse API Documentation API.

Create and reply to forum topics with Markdown via /posts.json and /t/{id}.json

Search topics, posts, and users via /search/query.json with category, tag, and user filters

Manage groups, group memberships, and category access through /groups and /admin/groups

GET STARTED

Start building with Discourse API Documentation API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Discourse API Documentation API for, with concrete tasks.

★ Customer Community and Support Forum Automation

Product teams running a Discourse community can automate the lifecycle of support topics - creating posts from inbound support tickets, tagging them, and notifying owners through group mentions. The /posts.json and /t/{id}.json endpoints handle topic creation and replies, while /search/query.json finds duplicate threads. This keeps the public knowledge base growing without manual triage.

POST /posts.json to create a new support topic with title, raw Markdown body, and category ID, then attach product-area tags via /t/{id}.json.

Community Events with Discourse Post Event Plugin

Communities using the discourse-post-event plugin can list, create, and export community events directly via the /discourse-post-event/events.json and /discourse-post-event/events.ics endpoints. Calendars can be embedded into external sites or pulled into personal calendars, giving members a single source of truth for meetups, AMAs, and office hours.

GET /discourse-post-event/events.json filtered to upcoming events for the 'meetups' category and render the response as a calendar widget.

Group Sync from External Identity Systems

Hosted Discourse customers can keep group membership in sync with HR systems, CRMs, or partner directories. PUT /groups/{id}/members and DELETE /groups/{id}/members add and remove users while /groups/{id}.json fetches state. This is commonly used to grant access to private categories based on subscription tier or role in another system.

Add user 'jane.doe' to the 'paid-customers' group via PUT /groups/{id}/members and confirm membership with GET /groups/{id}/members.

Forum Backups and Admin Automation

Hosted and self-hosted Discourse operators can automate routine admin work - triggering nightly backups via /admin/backups.json, downloading the latest backup file, and rotating retention. Category, badge, and group management can also be scripted from CI for reproducible community governance, especially when promoting changes from staging to production.

POST /admin/backups.json to trigger a fresh backup and poll until the file is available, then download via the returned filename.

AI Agent Community Assistant

AI agents can act as Discourse community helpers - answering recurring questions, posting daily summaries, and tagging stale topics - by calling the Discourse API through Jentic. The API-Key and API-Username headers stay in your Jentic One instance and never appear in the agent's context, while Jentic search lets the agent find the right topic or post operation by intent.

Search Jentic for 'reply to a Discourse topic', load the POST /posts.json operation, and execute it to post a daily community digest summary into the announcements category.

Key Endpoints

93 endpoints — discourse is the open-source forum software behind tens of thousands of communities, support sites, and product hubs.

METHOD

PATH

DESCRIPTION

POST

/posts.json

Create a new topic or reply to an existing topic

GET

/categories.json

List forum categories

GET

/discourse-post-event/events.json

List community events

GET

/discourse-post-event/events.ics

Export community events as iCal

PUT

/groups/{id}/members

Add members to a group

POST

/admin/backups.json

Trigger a forum backup

POST

/admin/badges.json

Create a new badge

POST

/posts.json

Create a new topic or reply to an existing topic

GET

/categories.json

List forum categories

GET

/discourse-post-event/events.json

List community events

GET

/discourse-post-event/events.ics

Export community events as iCal

PUT

/groups/{id}/members

Add members to a group

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Discourse API key and username are stored once, encrypted, by your own Jentic One instance and injected as the paired request headers at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a forum topic' or 'list community events', and Jentic returns the matching Discourse operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Discourse API Documentation API through Jentic.

What authentication does the Discourse API use?

Discourse uses two headers: API-Key (an admin or user-scoped key) and API-Username (the username the request acts on behalf of). Through Jentic, both values are held in your Jentic One instance and injected at execution; agents never see the raw key.

Can I list community events with the Discourse API?

Yes, when the discourse-post-event plugin is enabled. /discourse-post-event/events.json returns events as JSON and /discourse-post-event/events.ics returns the same set as an iCalendar feed for embedding in personal or external calendars.

What are the rate limits for the Discourse API?

Discourse enforces per-action rate limits configured by site settings such as max_requests_per_minute, max_post_creates_per_minute, and per-IP limits. Hosted plans publish defaults per tier. Inspect site settings or contact your Discourse hosting provider for the exact values applied to your forum.

How do I create a topic on Discourse through Jentic?

Search Jentic for 'create a topic on Discourse', load the POST /posts.json operation, and execute it with title, raw Markdown content, category ID, and any tags. Jentic returns the new topic's ID and slug for follow-up operations.

Can I export forum data with the Discourse API?

Yes, /admin/backups.json triggers a full forum backup, and /admin/backups/{filename} downloads a specific backup. Combined with category, topic, and user listing endpoints, you can also build incremental exports without invoking the full backup process.

Can I limit what my agent is allowed to do with the Discourse API?

Yes. Because your Jentic One instance is self-hosted, you decide which Discourse operations the agent can call and which stored API key and username it uses. You can allow only the operations it needs, such as creating a post via POST /posts.json or listing events via /discourse-post-event/events.json, while leaving broad admin operations like triggering backups through /admin/backups.json or creating badges via /admin/badges.json out of scope. Since a Discourse admin key grants wide forum access, this lets you narrow the agent to exactly the actions you approve.

Discourse API Documentation

Connect the Discourse API Documentation to your agent

Capabilities

Start building with Discourse API Documentation API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs