Webhooks for the HealthTasks REST API
The HealthTasks REST API now supports webhooks, so connected systems can react as soon as placements, schedules, compliance, or units change.
When we introduced the HealthTasks REST API, the goal was simple: connect clinical education data to the systems your program already runs.
That connection got stronger when clinical partners gained site-scoped access for placements, clearance, and unit updates. Schools and hospitals could share the same picture without overnight file drops.
Today that surface gets another step forward: webhooks.
Push when something changes
The REST API now supports optional webhooks. When placements, schedules, compliance, or units change, HealthTasks can notify your endpoint right away. Your systems learn that something moved, then pull the latest details from the API.
Configure an endpoint under Settings → REST API. Site-scoped connections only receive events for the locations they can access.
Why it matters
Pull-based sync already keeps school and hospital systems aligned. Webhooks make that loop tighter. Hospital schedulers and institutional tools can respond as soon as the roster, clearance status, or unit capacity updates. HealthTasks stays the system of record. Connected tools stay even closer to current.
Use webhooks alongside your existing sync. They are a faster signal on top of the API you already have.
Get started
Set up webhooks in HealthTasks under Settings → REST API. For setup details and the full API, see the documentation.
