Skip to content
Communication/messaging

mercure.local

The Mercure protocol sandbox and mock API

[Mercure](https://mercure.rocks) is a protocol allowing to push data updates to web browsers and other HTTP clients in a convenient, fast, reliable and battery-efficient way. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
5
Collections
-
Event types
-
Start this simulation
example request
curl https://your-mercure-local.slurry.io/.well-known/mercure \
  -H "Authorization: Bearer slurry_sim_..."

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

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

All 5.

  • GET/.well-known/mercure
  • POST/.well-known/mercure
  • GET/.well-known/mercure/subscriptions
  • GET/.well-known/mercure/subscriptions/{topic}
  • GET/.well-known/mercure/subscriptions/{topic}/{subscriber}