Skip to main content

Employees API

Create and prepare employees from job descriptions, files, or voice briefs. Employees are Assistant applications with an employee profile and shared knowledge, agents, permissions, and channels. Review tests before publishing the selected agent. See the Employee API overview for the lifecycle and visual walkthrough for screenshots.

📄️Enable or disable employee WhatsApp

Requires employee write access. Enabling requires a published employee and routes WhatsApp to its primary agent. New channels default to public access; isPublic=false limits access to application members. Omit isPublic to preserve a saved choice. Voice and credentials are preserved. Enabling Twilio without a number provisions a paid number and requires acknowledgeNumberPurchase=true. Meta and proxy connections require their existing provider setup. Disabling pauses the channel without releasing its number. The returned number can be used to generate a wa.me QR code; this is not account pairing.

📄️Enable or disable employee SMS

Requires employee write access. Enabling requires a published employee and routes SMS to its primary agent. New channels default to public access; isPublic=false limits access to application members with a matching phone number. Omit isPublic to preserve a saved choice. Enabling without a number provisions a paid US toll-free number on the Docana Twilio account and requires acknowledgeNumberPurchase=true; the number cannot send until Twilio approves its toll-free verification, which the returned verificationStatus tracks. Disabling pauses the channel without releasing its number.

📄️Prepare employee from message

Uses the same employee preparation assistant as the UI. Send a goal or correction; optionally continue a caller-owned preparation thread. Can write drafts, configure connections and run authorized tests. Publishes only after explicit user approval. May take several minutes. With Prefer: respond-async, returns 202 once the brief is saved; the response continues in the returned preparation thread. After a timeout or interrupted write, inspect employee status and thread history before retrying. Enter website credentials through the dedicated login operation or secure form, not the prompt.