Skip to main content
WireDesk is set up in the dashboard. As a developer, you usually have one of three jobs: put the chat widget on a site and wire it into that site’s UI, let the agent call your own systems mid-conversation, or answer a security review. This tab covers all three.

​
What you can integrate with

​
What does not exist yet

WireDesk has no public REST API and no outbound webhooks. You cannot pull conversations with an API key or subscribe to events on your server. The /api/… routes the dashboard uses need a signed-in session, and they are not a supported interface. Today you have two ways to get data out:
  • API call actions push data out while the conversation happens. The agent calls your endpoint with the parameters you declared, so a lead or an order query can reach your CRM or backend straight away. See API calls.
  • CSV exports get the history out afterwards. Conversations, contacts, leads and collected data each have an export in the dashboard. See Exports.
The widget’s events run in the visitor’s browser, not on your server. Use them for page-level analytics, not as a record of every conversation.

​
Docs for tools and AI assistants

The docs are published in plain-text forms too:
  • https://wiredesk.ai/docs/llms.txt is an index of every page in these docs, in the llms.txt format.
  • Add .md to the end of any docs page URL to get that page as Markdown, e.g. https://wiredesk.ai/docs/widget/install.md.
Point a coding assistant at these instead of the rendered HTML.

​
Developer pages

JavaScript API

Open, close and drive the widget from your own code.

Widget settings

Every wiredeskSettings field and data-* attribute, with defaults and precedence.

Events

What the widget emits, when, and with what payload.

Verified visitors

Sign a user id on your server so the agent knows who is chatting.

Security model

Keys, domains, identity, iframe isolation, rate limits and outbound calls.

Direct trunk

Route calls from your own SIP trunk to the agent.