Skip to content
Communication/messaging

twitter.com:current

Twitter API v2 sandbox and mock API

Twitter API v2 available endpoints Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
80
Collections
-
Event types
-
Start this simulation
example request
curl https://your-twitter-current.slurry.io/2/compliance/jobs \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2.61.

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

  • GET/2/compliance/jobs
  • POST/2/compliance/jobs
  • GET/2/compliance/jobs/{id}
  • POST/2/dm_conversations
  • GET/2/dm_conversations/with/{participant_id}/dm_events
  • POST/2/dm_conversations/with/{participant_id}/messages
  • POST/2/dm_conversations/{dm_conversation_id}/messages
  • GET/2/dm_conversations/{id}/dm_events
  • GET/2/dm_events
  • POST/2/lists
  • GET/2/lists/{id}
  • PUT/2/lists/{id}