Developers
Build on EveryChan
EveryChan has a REST API, outbound webhooks, an OAuth provider for building installable apps, and an embeddable chat widget with a small JavaScript API. This is where you wire EveryChan into the rest of your stack.
Base URL & format
Every REST endpoint lives under /api on your app host. On staging that is:
https://everychan-app.dashka.io/apiRequests and responses are JSON. Successful responses wrap their payload in a data field; errors return a non-2xx status with an error string.
Quickstart
Issue a visitor token (this endpoint is public — it is what the widget calls to start a session), then open a conversation over the WebSocket. For agent-side and management calls, authenticate with a bearer token — see Authentication.
# 1. Get a visitor session token
curl -X POST https://everychan-app.dashka.io/api/visitors/get_token \
-H "Content-Type: application/json" \
-d '{"workspaceId":"YOUR_WORKSPACE_ID"}'
# → { "data": { "token": "…", "visitorSessionId": "…", "workspaceId": "…" } }
# 2. Call an authenticated endpoint
curl https://everychan-app.dashka.io/api/canned-responses \
-H "Authorization: Bearer YOUR_TOKEN"What you can build
- Installable apps — register an OAuth app and let any workspace install it with scoped access (the model Slack, HubSpot, etc. use).
- Event-driven automations — subscribe to webhooks for new conversations, messages, and closes.
- Custom widgets & deep links — embed the chat widget and drive it from your own UI.
API reference
Every endpoint is documented interactively — authenticate with a token and try calls right in the browser.