What this is: A read-only quickstart for Synchronizer API (dental PMS integrations). The 3-minute video shows account setup and core concepts, then you run five GETs to validate scheduling semantics before writing business logic.
How to try (requires free dev signup to get a token)
Create dev account: get sandbox token
Fork the Postman collection: set env vars BASE_URL, TOKEN, location_id, and subdomain
Run (read-only)
GET /locations?subdomain={{subdomain}}
GET /providers?location_id={{location_id}}
GET /availabilities?subdomain?subdomain={{subdomain}}&location_id={{location_id}}&page=1&per_page=5&active=true&ignore_past_dates=false
GET /appointment_slots?subdomain=test&start_date={{startIso}}&days=10&lids[]={{location_id}}&pids[]={{provider_id}}&overlapping_operatory_slots=false
GET /appointments/{{appt_id}}
What to look for
Appointment slots show actual calendar availability (no guesswork)
Appointment details shows CONFIRMED/ PATIENT_MISSED/ CANCELED as events
Behavior is consistent across locations/time windows
How to try (requires free dev signup to get a token) Create dev account: get sandbox token
Fork the Postman collection: set env vars BASE_URL, TOKEN, location_id, and subdomain
Run (read-only)
GET /locations?subdomain={{subdomain}} GET /providers?location_id={{location_id}} GET /availabilities?subdomain?subdomain={{subdomain}}&location_id={{location_id}}&page=1&per_page=5&active=true&ignore_past_dates=false GET /appointment_slots?subdomain=test&start_date={{startIso}}&days=10&lids[]={{location_id}}&pids[]={{provider_id}}&overlapping_operatory_slots=false GET /appointments/{{appt_id}}
What to look for Appointment slots show actual calendar availability (no guesswork)
Appointment details shows CONFIRMED/ PATIENT_MISSED/ CANCELED as events
Behavior is consistent across locations/time windows