doo provides an event-driven API that allows synchronizing doo resources to external systems using webhooks. Each time a resource is changed, doo will call the respective API endpoint of the external system.

See sub-pages to find more details.

Basic webhook flow

  1. A user change resource in doo, which fires one or more webhooks

  2. For each webhook, if an external webhook API endpoint has been configured:

    1. doo authenticates with the external authorization endpoint to retrieve an access token;

    2. doo sends a webhook request to the external endpoint with the resource in its payload;

    3. external system processes webhook payload.

Typical system setup

A typical integration scenario consists of the customer's Content Management System (CMS), which uses doo widgets to enable attendees to book, and the customer's Customer Relationship Management (CRM) as an external system, which provides endpoints for doo webhooks.