Skip to content
Calendar & scheduling

developer.calendly.com

Calendly sandbox and mock API

A realistic Calendly workspace for a 40-50 person distributed UK/US business with multiple teams, recurring meetings, and active scheduling activity throughout the working day. Writes persist, data moves on a schedule and every change can fire a signed webhook.

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

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

  • GET/activity_log_entries
  • GET/user_availability_schedules/{uuid}
  • GET/event_type_availability_schedules
  • PATCH/event_type_availability_schedules
  • GET/user_availability_schedules
  • GET/user_busy_times
  • GET/contacts
  • POST/contacts
  • GET/contacts/{uuid}
  • PATCH/contacts/{uuid}
  • DELETE/contacts/{uuid}
  • GET/contacts/custom_field_definitions/{uuid}