Skip to content
Communication/messaging

developers.intercom.com

Intercom sandbox and mock API

The intercom API reference. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
231
Collections
-
Event types
-
Start this simulation Vendor documentation
example request
curl https://your-intercom.slurry.io/me \
  -H "Authorization: Bearer slurry_sim_..."

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

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

  • GET/me
  • GET/macros/{id}
  • GET/macros
  • PUT/admins/{admin_id}/away
  • GET/admins/activity_logs
  • POST/admins/activity_logs/search
  • GET/admins/activity_log_event_types
  • GET/admins
  • GET/office_hours_schedules/{office_hours_schedule_id}/office_hours_exceptions/{id}
  • PUT/office_hours_schedules/{office_hours_schedule_id}/office_hours_exceptions/{id}
  • DELETE/office_hours_schedules/{office_hours_schedule_id}/office_hours_exceptions/{id}
  • GET/office_hours_schedules/{office_hours_schedule_id}/office_hours_exceptions
Intercom sandbox and mock API | Slurry