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

DevelopersAPI keys and the REST API are on the Starter plan and above. On Free, a new key cannot be made and calls with a key are refused with the reason; webhooks work on every plan.
Making a key
- A new key only reads unless you switch on May write. Write lets it create and change contacts, add tags, record events, update products and manage webhook subscriptions; give it only to a key that needs it.
- Every key expires: after 30 days, 90 days or 1 year (the default and the longest). An expired key is refused; make a new one and swap it in.
- Allowed addresses (optional): the IP addresses the key may be used from, at most 20, one per line or separated by commas. IPv4 (203.0.113.7), IPv6 (2001:db8::1), or the start of an IPv4 address ending in a dot (203.0.113. for the whole block). Empty means any address.
- The key itself is shown once, when it is made. The list shows when each key was made, when it expires, when it was last used, how many requests it has made and where it may be used from. Revoke stops a key at once and cannot be undone.
Usage and pauses
Under the keys, Usage shows the workspace’s API for the last 7 days (by UTC day): requests, refused requests, writes, and emails started through the API. If doTask suspends the API for a workspace, or pauses emails started through the API after an unusual spike, the page says so; write to [email protected] to have it looked at.
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 or by phone alone in E.164 (+60123456789) — name, tags, properties; consent true subscribes them to email, whatsapp_opt_in true records their WhatsApp consent with source api and the time. 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.