Buy credits once and use them when you need them. There are no monthly tiers, and credits do not expire.
Discourse API Discourse Search API for niche community mention tracking
Use SocialListeningAPI to find people talking about your brand inside public niche Discourse forums. Search one forum by URL and keyword, then get newest-first posts with topic, author, category, engagement, and source URL data.
- Find brand mentions inside niche communities
- Catch product questions, complaints, and feature requests
- Keep topic, category, author, and source URL context
{
"success": true,
"platform": "discourse",
"endpoint": "/api/v1/discourse/search",
"data": {
"items": [
{
"id": "discourse.32bit.cafe:8057",
"platform": "discourse",
"url": "https://discourse.32bit.cafe/t/32-bit-cafe-joins-the-fediverse/1173/1",
"content": {
"title": "32-Bit Cafe Joins the Fediverse!",
"text": "The 32-Bit Cafe is joining the fediverse with its own Pixelfed instance.",
"media_urls": [],
"thumbnail_url": null
},
"author": {
"id": "xandra",
"username": "xandra",
"display_name": "xandra",
"avatar_url": "https://discourse.32bit.cafe/user_avatar/discourse.32bit.cafe/xandra/96/5075_2.png",
"verified": null
},
"engagement": {
"views": null,
"likes": 17,
"comments": null,
"shares": null,
"saves": null
},
"published_at": "2024-08-06T20:20:28.409Z",
"ext": {
"forum_url": "https://discourse.32bit.cafe",
"author_url": "https://discourse.32bit.cafe/u/xandra",
"topic_id": 1173,
"topic_slug": "32-bit-cafe-joins-the-fediverse",
"post_number": 1,
"category_id": 5,
"category_name": null,
"category_slug": null,
"topic_posts_count": 28,
"topic_reply_count": 16,
"tags": []
}
}
]
},
"pagination": {
"next_cursor": "2",
"has_more": true,
"page_size": 1
},
"raw": {
"posts": [
{
"id": 8057,
"username": "xandra",
"avatar_template": "/user_avatar/discourse.32bit.cafe/xandra/{size}/5075_2.png",
"created_at": "2024-08-06T20:20:28.409Z",
"like_count": 17,
"blurb": "The 32-Bit Cafe is joining the fediverse with its own Pixelfed instance.",
"post_number": 1,
"topic_id": 1173
}
],
"topics": [
{
"id": 1173,
"title": "32-Bit Cafe Joins the Fediverse!",
"slug": "32-bit-cafe-joins-the-fediverse",
"posts_count": 28,
"reply_count": 16,
"category_id": 5,
"tags": []
}
],
"categories": [],
"grouped_search_result": {
"more_full_page_results": true
}
},
"request_id": "req_example123",
"credits_used": 1,
"credits_remaining": 99
}What does the Discourse Search API return?
Pass a public Discourse forum URL and a keyword or phrase. The endpoint searches that forum's posts, sorts matches newest first, and returns normalized JSON. Use the returned cursor to request another page when one is available. Each successful request costs 1 credit.
Results can include the topic title, matching post text, author, avatar, likes, publication time,
category, tags, topic and reply counts, author URL, and direct post URL. Set raw to
true when you need the forum's unchanged search response.
The endpoint searches one known forum per request. It does not discover forums, search private areas, promise complete coverage, or provide native scheduling, alerts, sentiment analysis, or reply automation. Public search availability depends on each forum.
Why niche community mentions are useful
A niche forum gives a mention useful context. You can see the topic title, category, tags, nearby problem, and direct source URL. That helps you separate a real product question from an unrelated use of the same word.
Discourse describes its communities as places for support, product feedback, and developer discussion. Its official platform overview reports more than 22,000 communities. These forums often keep detailed, searchable discussions that are easy to miss in short social feeds.
Start with exact brand and product names. Then add competitor names, common misspellings, product category terms, and problem phrases. Discourse also documents category, tag, date, and order search filters for forums that support them.
Try the Discourse Search API
Choose cURL, Axios, or fetch. Add your API key, forum URL, keyword, and optional cursor.
curl --get 'https://api.sociallisteningapi.com/api/v1/discourse/search' \
--data-urlencode 'url=https://discourse.32bit.cafe' \
--data-urlencode 'query=social listening' \
--data-urlencode 'exact=true' \
--data-urlencode 'cursor=2' \
--data-urlencode 'raw=true' \
--header 'x-api-key: YOUR_API_KEY'Why use SocialListeningAPI for Discourse search?
Search niche public forums with the same API key and credit balance used for public social posts, videos, profiles, and Google results.
Each API returns the same core response shape, so you do not need separate parsing code for every source.
Search public social posts, videos, profiles, Google results, and Discourse forums with one API key.
Failed requests do not use credits. A successful response uses the endpoint's listed credit cost.
Keep available post URLs beside results for review, citations, and follow-up work.
Use normalized fields in your app and inspect the raw provider response when you need more detail.
Playbooks
Use Discourse search in a practical workflow
Follow a playbook to turn public questions into a community FAQ, find product misconceptions, or build externally scheduled brand mention alerts.
Choose the right route
SocialListeningAPI vs direct Discourse search
SocialListeningAPI fits products that need normalized forum results beside other public sources. Direct forum search fits a one-site integration when you can handle each forum's access, response, and changes yourself.
SocialListeningAPI
Search a public Discourse forum with one server-side API key.
- Pass a public forum URL and keyword
- Get normalized topic, post, author, category, and source data
- Use a cursor when another result page is available
- Pay 1 credit for each successful request
Direct Discourse search
Call each forum's search route yourself when you only need one site and can maintain the integration.
- Work with each forum's URL, access rules, and response shape
- Use Discourse search syntax for categories, tags, and dates
- Handle forum errors, response changes, and normalization
- Choose this route when a shared multi-source schema is unnecessary
MCP integration
Give social listening powers to your chat app
Connect SocialListeningAPI to Claude or ChatGPT. Ask a question in plain language, get actual, realtime results from social media platforms, forums and serps - with source links.
Use it to get brand mentions, scope out competitors, find leads and more - all from within your chat app.
See how the MCP worksClaude · SocialListeningAPI connected
MCP toolsearch_social_posts
reddit · "social listening API cost"Public posts returned with source URLs · 1 credit
1 credit per successful forum search
Buy a one-time credit pack and use it across every API. Credits do not expire.
Starter
$20one time
5,000 credits A simple pack for testing the API and smaller projects.
- $0.0040 per credit
- Use credits across every API endpoint
- Credits never expire
Growth Best value
$100one time
40,000 credits More credits at a lower cost for apps making regular calls.
- $0.0025 per credit
- Use credits across every API endpoint
- Credits never expire
Discourse Search API questions
Can I find brand mentions in public Discourse forums?
Does the API search every Discourse forum at once?
Can it search private forums or private categories?
What fields does a Discourse result include?
Does Discourse search support pagination?
What does one Discourse search cost?
Does SocialListeningAPI send alerts for new forum mentions?
Search your first niche Discourse forum
Create an account, copy your API key, and use 100 free credits to test public forum search.