Skip to content
Communication/messaging

googleapis.com

Test against the Gmail API

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

Operations
30
Start this simulation Vendor documentation
example request
curl https://your-gmail.slurry.io/gmail/v1/users/123/drafts \
  -H "Authorization: Bearer slurry_sim_live_..."

Your simulation gets its own hostname, key and IP allow-list. Spec snapshot: version v1.

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

  • GET/gmail/v1/users/{userId}/drafts
  • POST/gmail/v1/users/{userId}/drafts
  • POST/gmail/v1/users/{userId}/drafts/send
  • GET/gmail/v1/users/{userId}/drafts/{id}
  • PUT/gmail/v1/users/{userId}/drafts/{id}
  • DELETE/gmail/v1/users/{userId}/drafts/{id}
  • GET/gmail/v1/users/{userId}/history
  • GET/gmail/v1/users/{userId}/labels
  • POST/gmail/v1/users/{userId}/labels
  • GET/gmail/v1/users/{userId}/labels/{id}
  • PUT/gmail/v1/users/{userId}/labels/{id}
  • PATCH/gmail/v1/users/{userId}/labels/{id}

Does this simulation differ from the real Gmail 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