Developers

API keys, webhooks and project identifiers

The REST API and its specification, signed webhooks, and the ids a developer needs.

Two colleagues working through a plan together
Developers
Read it in the appThe same article opens from Help inside app.dotask.io, beside the screen it describes.

Your own booking system, POS or website

Two calls let any system you already run feed the dashboard and start email automations, with no widget needed. POST /v1/api/contacts creates or updates a person by email (name, phone, tags, properties; consent true subscribes them). POST /v1/api/events says something happened to them — {"email", "name", "event": "booking.completed", "ref": "BK-1042", "occurred_at", "data": {"service": "COCOScalp Treatment", "branch": "Platinum Park", "amount": 180}} — kept once per ref, and an automation with the trigger “an event from your own system: booking.completed” runs for every one, with each data field as {{data.service}} in the emails. The event name is yours to choose; the ones received appear as suggestions in the automation editor. Both need a key with the write scope. Settings → Developers → dotaskAPI has the exact shapes and a copy-ready example.

  • dotaskAPI — create keys for the REST API; its specification file (OpenAPI format) is linked from the same page. Served by the doTask API server, not by this dashboard.
  • Webhooks — signed POSTs to your endpoints when something happens (a booking, a handoff, a new contact); each delivery is listed with its status so failures are visible.
  • Project — workspace and channel identifiers. None is secret; keys and webhook secrets live on their own pages.