Skip to documentation

Developer integrations

Use the supported context hooks and understand the server integration boundaries.

5 practical guides

Build around supported boundaries.

The supported integration surfaces serve different purposes. Installation values connect the public website. Browser context improves relevance and remains untrusted. Trusted context comes from your backend through a separately arranged site credential and conversation-mapping lifecycle. Actions call a fixed configured provider contract. Keeping these surfaces separate makes both implementation and security review more predictable.

Start with browser context and field definitions for page relevance. If authenticated account facts are needed, read the trusted-context prerequisites before writing attachment code: the stock widget does not provide a public conversation-ID callback. Use the request reference for diagnosis without depending on private widget state or portal internals as stable APIs. Document which system authenticates the customer, authorizes each record and owns each secret.

Public hints and trusted factsA quick view
  1. DefineEnabled fields and expected types
  2. SupplyPublic hints or authorized server facts
  3. ValidateWebsite and conversation boundaries
  4. UseRelevant answers within configured capabilities

An input’s origin determines what it can establish; a browser value is not account authorization.

Guide 7 min read

Provide browser context

Use reesponderContext, setContext, clearContext and the ready event without treating browser values as verified identity.

Read the guide
Guide 7 min read

Design context fields

Define useful, typed website context and understand the limits of sensitivity and retention metadata.

Read the guide
Guide 7 min read

Provide trusted server context

Attach configured backend facts to a conversation using a website-scoped bearer credential and an authorized server integration.

Read the guide
Guide 7 min read

Supported integration boundaries

Distinguish the website widget, server integration contracts, provider endpoints and internal workspace API routes.

Read the guide
Guide 7 min read

Widget request and error reference

Recognize the official widget's installation, bootstrap and message requests when inspecting a browser network trace.

Read the guide
Browse all documentation

Your website.
A useful conversation away.

Use the installation guide to get started, or ask our team about the setup your business needs.

Open the installation guide Talk to our team

Search documentation

Search by task, feature, setting or error. Your search runs in this browser.