Communication/messaging
twitter.com:legacy
Twitter sandbox and mock API
A hosted, stateful simulation shaped like the Twitter API. Writes persist, data moves on a schedule and every change can fire a signed webhook.
- Operations
- 83
- Collections
- -
- Event types
- -
example request
curl https://your-twitter-legacy.slurry.io/1.1/account/settings.json \
-H "Authorization: Bearer slurry_sim_..."Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.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 83.
- GET/account/settings.json
- POST/account/settings.json
- POST/account/update_delivery_device.json
- POST/account/update_profile.json
- POST/account/update_profile_background_image.json
- POST/account/update_profile_colors.json
- POST/account/update_profile_image.json
- GET/application/rate_limit_status.json
- POST/blocks/create.json
- POST/blocks/destroy.json
- GET/blocks/ids.json
- GET/blocks/list.json