File storage & documents
graph.microsoft.com
Test against the Microsoft Graph OneDrive API
A hosted, stateful simulation shaped like the Microsoft Graph OneDrive API. Writes persist, data moves on a schedule and every change can fire a signed webhook. Unofficial: not affiliated with graph.microsoft.com.
- Operations
- 10
example request
curl https://your-onedrive.slurry.io/v1.0/me/drive \
-H "Authorization: Bearer slurry_sim_live_..."Your simulation gets its own hostname, key and IP allow-list. Spec snapshot: version v1.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
All 10.
- GET/me/drive
- GET/me/drives
- GET/me/drive/root
- GET/me/drive/root/children
- POST/me/drive/root/children
- GET/me/drive/items/{item-id}
- PATCH/me/drive/items/{item-id}
- DELETE/me/drive/items/{item-id}
- GET/me/drive/items/{item-id}/children
- POST/me/drive/items/{item-id}/children
Does this simulation differ from the real Microsoft Graph OneDrive API?
Tell us about wrong response shapes, status codes, missing endpoints or unrealistic data. If you have a simulation of it, report from its Issues tab so we can see the exact call.