Skip to content
Other

hillbillysoftware.com:shinobi

shinobiapi sandbox and mock API

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

Operations
58
Collections
-
Event types
-
example request
curl https://your-hillbillysoftware-shinobi.slurry.io/Actors/Search/123/123 \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/Actors/Search/{accesstoken}/{Query}
  • POST/AddActor
  • POST/AddTVShow
  • GET/Aliases/ByID/{AccessToken}/{imdbID}
  • GET/Aliases/ByName/{AccessToken}/{Title}
  • GET/Awards/ByWinner/{AccessToken}/{Nominee}
  • GET/Awards/ByYear/{Year}
  • GET/Calendar/ByDate/{AccessToken}/{Date}/{Country}
  • GET/Calendar/Countries/{AccessToken}
  • GET/Calendar/Networks/{AccessToken}
  • GET/Calendar/Seasons/{AccessToken}/{Name}
  • GET/Calendar/Show/Season/{AccessToken}/{Name}/{Season}