Skip to content
Communication/messaging

dev.to

Forem API V1 sandbox and mock API

Access Forem articles, users and other resources via API. For a real-world example of Forem in action, check out [DEV](https://www.dev.to). All endpoints can be accessed with the 'api-key' header and a accept header, but some of them are accessible publicly without authentication. Dates and date times, unless otherwise specified, must be in the [RFC 3339](https://tools.ietf.org/html/rfc3339) forma Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
40
Collections
-
Event types
-
Start this simulation
example request
curl https://your-dev-to.slurry.io/api/api/articles \
  -H "Authorization: Bearer slurry_sim_..."

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

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 40.

  • POST/api/admin/users
  • GET/api/articles
  • POST/api/articles
  • GET/api/articles/latest
  • GET/api/articles/me
  • GET/api/articles/me/all
  • GET/api/articles/me/published
  • GET/api/articles/me/unpublished
  • GET/api/articles/{id}
  • PUT/api/articles/{id}
  • PUT/api/articles/{id}/unpublish
  • GET/api/articles/{username}/{slug}