Discourse API Documentation

api:discourse.local · vlatest · source: apis.guru

This page contains the documentation on how to use Discourse through API calls. Note: For any endpoints not listed you can follow the reverse engineer the Discourse API guide to figure out how to use an API endpoint. Request Content-Type The Content-Type for POST and PUT requests can be set to application/x-www-form-urlencoded , multipart/form-data , or application/json . Endpoint Names and Response Content-Type Most API endpoints provide the same content as their HTML counterparts. For example the URL /categories serves a list of categories, the /categories.json API provides the same information in JSON format. Instead of sending API requests to /categories.json you may also send them to /categories and add an Accept: application/json header to the request to get the JSON response. Sending requests with the Accept header is necessary if you want to use URLs for related endpoints returned by the API, such as pagination URLs. These URLs are returned without the .json prefix so you need to add the header in order to get the correct response format. Authentication Some endpoints do not require any authentication, pretty much anything else will require you to be authenticated. To become authenticated you will need to create an API Key from the admin panel. Once you have your API Key you can pass it in along with your API Username as an HTTP header like this: curl -X GET "http://127.0.0.1:3000/admin/users/list/active.json" \ -H "Api-Key: 714552c6148e1617aeab526d0606184b94a80ec048f

[![Connect-MCP](https://clawy.uk/mcp/badge/api%3Adiscourse.local.svg)](https://clawy.uk/mcp/s/api%3Adiscourse.local)