Skip to content
Cloud infrastructure/devops

ritc.io

Ritc sandbox and mock API

Rules in the Cloud Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
66
Collections
-
Event types
-
example request
curl https://your-ritc.slurry.io/actions \
  -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 66.

  • GET/actions
  • POST/actions
  • GET/actions/{action_id}
  • PATCH/actions/{action_id}
  • DELETE/actions/{action_id}
  • GET/admin
  • POST/admin/log
  • GET/admin/ping
  • GET/apps
  • POST/apps
  • GET/apps/channels/users
  • GET/apps/channels/{channel_id}/users