Skip to content
Communication/messaging

graph.microsoft.com

Test against the Microsoft Graph Teams API

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

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

  • GET/chats
  • POST/chats
  • GET/chats/{chat-id}
  • PATCH/chats/{chat-id}
  • DELETE/chats/{chat-id}
  • GET/chats/{chat-id}/members
  • POST/chats/{chat-id}/members
  • GET/chats/{chat-id}/messages
  • POST/chats/{chat-id}/messages
  • GET/chats/{chat-id}/messages/{chatMessage-id}
  • PATCH/chats/{chat-id}/messages/{chatMessage-id}
  • DELETE/chats/{chat-id}/messages/{chatMessage-id}

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