Skip to content
Cloud infrastructure/devops

crucible.local

Crucible sandbox and mock API

A hosted, stateful simulation shaped like the Crucible API. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
79
Collections
-
Event types
-
Start this simulation
example request
curl https://your-crucible-local.slurry.io/context/rest-service/auth-v1/login \
  -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 79.

  • GET/rest-service/auth-v1/login
  • POST/rest-service/auth-v1/login
  • GET/rest-service/projects-v1
  • GET/rest-service/projects-v1/{key}
  • GET/rest-service/repositories-v1
  • GET/rest-service/repositories-v1/browse/{repository}/{path}
  • GET/rest-service/repositories-v1/change/{repository}/{revision}
  • GET/rest-service/repositories-v1/changes/{repository}/{path}
  • GET/rest-service/repositories-v1/content/{repository}/{revision}/{path}
  • GET/rest-service/repositories-v1/history/{repository}/{revision}/{path}
  • GET/rest-service/repositories-v1/{repository}
  • GET/rest-service/repositories-v1/{repository}/svn