Skip to content
Cloud infrastructure/devops

maif.local:otoroshi

Otoroshi Admin sandbox and mock API

Admin API of the Otoroshi reverse proxy Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
102
Collections
-
Event types
-
Start this simulation
example request
curl https://your-maif-local-otoroshi.slurry.io/api/apikeys \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/api/apikeys
  • GET/api/auths
  • POST/api/auths
  • GET/api/auths/{id}
  • PUT/api/auths/{id}
  • PATCH/api/auths/{id}
  • DELETE/api/auths/{id}
  • GET/api/certificates
  • POST/api/certificates
  • GET/api/certificates/{id}
  • PUT/api/certificates/{id}
  • PATCH/api/certificates/{id}