Skip to content
Communication/messaging

discourse.local

Discourse API Documentation sandbox and mock API

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](https://meta.discourse.org/t/-/20576) 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`, Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
84
Collections
-
Event types
-
Start this simulation
example request
curl https://your-discourse-local.slurry.io/admin/backups.json \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version latest.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 84.

  • GET/admin/backups.json
  • POST/admin/backups.json
  • GET/admin/backups/{filename}
  • PUT/admin/backups/{filename}
  • GET/admin/badges.json
  • POST/admin/badges.json
  • PUT/admin/badges/{id}.json
  • DELETE/admin/badges/{id}.json
  • POST/admin/groups.json
  • DELETE/admin/groups/{id}.json
  • GET/admin/users/list/{flag}.json
  • GET/admin/users/{id}.json