Skip to content
Identity & SSO

graph.microsoft.com

Test against the Microsoft Graph API

A hosted, stateful simulation shaped like the Microsoft Graph API. Writes persist, data moves on a schedule and every change can fire a signed webhook. Unofficial: not affiliated with graph.microsoft.com.

Operations
178
Start this simulation Vendor documentation
example request
curl https://your-microsoft-graph.slurry.io/v1.0/users \
  -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

First 12 of 178.

  • GET/groups
  • POST/groups
  • GET/groups/{group-id}
  • PATCH/groups/{group-id}
  • DELETE/groups/{group-id}
  • GET/groups/{group-id}/members
  • GET/groups/delta()
  • GET/users
  • POST/users
  • GET/users/{user-id}
  • PATCH/users/{user-id}
  • DELETE/users/{user-id}

Does this simulation differ from the real Microsoft Graph 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.

Sign in to report an issue
Test against the Microsoft Graph API: stateful simulation | Slurry