Skip to content
Helpdesk & ticketing

developer.zendesk.com

Zendesk sandbox and mock API

Zendesk Support API endpoints Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
600
Collections
-
Event types
-
Start this simulation Vendor documentation
example request
curl https://your-zendesk.slurry.io/api/v2/account/email_settings \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2.0.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 600.

  • GET/api/v2/{target_type}/{target_id}/relationship_fields/{field_id}/{source_type}
  • GET/api/v2/account/email_settings
  • PUT/api/v2/account/email_settings
  • GET/api/v2/account/settings
  • PUT/api/v2/account/settings
  • POST/api/v2/accounts
  • GET/api/v2/accounts/available
  • GET/api/v2/activities
  • GET/api/v2/activities/{activity_id}
  • GET/api/v2/activities/count
  • POST/api/v2/any_channel/channelback/report_error
  • POST/api/v2/any_channel/push