Skip to content
Cloud infrastructure/devops

files.com

Files.com sandbox and mock API

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

Operations
222
Collections
-
Event types
-
Start this simulation
example request
curl https://your-files.slurry.io/api/rest/v1/action_notification_export_results \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/action_notification_export_results
  • POST/action_notification_exports
  • GET/action_notification_exports/{id}
  • POST/action_webhook_failures/{id}/retry
  • GET/api_key
  • PATCH/api_key
  • DELETE/api_key
  • GET/api_keys
  • POST/api_keys
  • GET/api_keys/{id}
  • PATCH/api_keys/{id}
  • DELETE/api_keys/{id}
Files.com sandbox and mock API | Slurry