Firehouse Solutions
Web Design and Data Management for Firefighters, Rescue Techs, EMTS, Medics, and All Others Who Save Lives
Phone 301.475.1900
Web Design and Data Management for Firefighters, Rescue Techs, EMTS, Medics, and All Others Who Save Lives Phone 301.475.1900   
Firehouse Solutions Firehouse Solutions


August 15, 2026:
Training Center Now Available
April 20, 2026:
Release of AI Writing Tool and Two-Factor Authentication
October 30, 2025:
Schedule News Posts for Automated Go Live and Come Down
August 30, 2025:
Light and Dark Mode, Calendar Email Reminders, Emoji Support, and Video Galleries
October 17, 2024:
Why Your Organization Needs Email Archiving
February 5, 2024:
Introducing Upgraded SmarterMail and firehouse.email
API: Discussion Forum

« Back to the API Documentation overview - authentication, security, response codes, and the full endpoint list.

Online and locked topics. Pass ID to get a single topic with its replies (returned in items[]; the topic itself is returned in a topic object).

HTTP Request TypeGET
Calling URIhttps://www.YourDepartment.com/apps/api/discuss/
Request HeaderAuthorization: Bearer {access_token}
Success Codes200 OK
Failure Codes400, 401, 403, 404, 405, 429, 500 - see the error reference

Parameters
ParameterDescription
ID Optional. A Topic_ID; response then contains the topic plus its replies.
StartDate / EndDate Optional. Filter topic list by last-post date (yyyy-mm-dd).

All data endpoints also accept the common MaxRows (default 100, maximum 500) and StartRow paging parameters.

Response Properties
PropertyDescription
Topic_ID / Topic_Title Topic ID and title
Topic_Locked 1 = topic is locked (number)
Topic_CreatedDate / Topic_LastPostDate Dates (string)
Author Topic or reply author (string)
ReplyCount List mode: number of online replies (number)
Reply_ID / Reply_Text / Reply_CreatedDate Single-topic mode: each item is one reply

Records are returned in the items array of the standard response envelope.


Sample Code

Exchange your refresh token for an access token, then request data. The same two steps work in any language; JavaScript and Python are shown here.

JavaScript
const BASE = "https://www.YourDepartment.com/apps/api";
const REFRESH_TOKEN = "your-refresh-token-here";

// 1. Exchange the refresh token for an access token (do this from a server,
//    not from a public web page, so the refresh token stays secret)
const tokenRes = await fetch(`${BASE}/refresh/`, {
    method: "POST",
    headers: { "Authorization": `Bearer ${REFRESH_TOKEN}` }
});
const tokenData = await tokenRes.json();

// 2. Call the discuss endpoint (reuse the token for up to 24 hours)
const res = await fetch(`${BASE}/discuss/?MaxRows=10`, {
    headers: { "Authorization": `Bearer ${tokenData.access_token}` }
});
const data = await res.json();

data.items.forEach(item => console.log(item));

Python
import requests

BASE = "https://www.YourDepartment.com/apps/api"
REFRESH_TOKEN = "your-refresh-token-here"

# 1. Exchange the refresh token for an access token
token = requests.post(f"{BASE}/refresh/",
    headers={"Authorization": f"Bearer {REFRESH_TOKEN}"}).json()

# 2. Call the discuss endpoint (reuse the token for up to 24 hours)
data = requests.get(f"{BASE}/discuss/",
    params={"MaxRows": 10},
    headers={"Authorization": f"Bearer {token['access_token']}"}).json()

for item in data["items"]:
    print(item)