Channel APIs will cover how conversations enter and leave Woes. Channel administration should be separate from browser-facing widget routes.
Planned resources
| Resource | Description |
|---|
| Widget configuration | Public key, install readiness, and deployment metadata. |
| Widget sessions | Browser conversation session state and safe metadata. |
| Discord configuration | Installation and channel mapping status. |
| Email domain status | Verified domains and outbound test readiness. |
| Channel availability | Whether a channel is ready for customer traffic. |
| Identity mappings | Channel-specific customer identity links. |
Current boundaries
| Channel | Current expectation |
|---|
| Live chat | Active inbound channel through the Woes widget. |
| Discord | Active inbound channel when connected. |
| Email | Verified domains and outbound tests; inbound intake is not generally available. |
Common use cases
- Read widget readiness for a deployment checklist.
- Show channel status in an internal admin page.
- Confirm Discord mappings before launch.
- Check email domain readiness.
- Connect channel identities to customer profiles.
Widget public routes should remain narrower than authenticated channel administration APIs.
