Bootstrap the widget on a visitor's page
Called from the visitor’s browser before the launcher renders: confirms the embed is live and returns the brand to draw it with. Takes a widget key, no API key.
GET
Call this from the visitor’s browser when your page loads, before you render the widget launcher. It does not take an API key or a console session. It takes the embed’s public widget key in the
X-ARUKZ-Widget-Key header, and the browser’s Origin must be allowed by both the deployment’s allowed_origins and the platform-wide widget allowlist. See Website widget.
A 200 is the whole answer: it proves the key names a live deployment, the page’s origin is permitted and the organization is active. status is always active. The response deliberately says nothing about the organization, the assistant or the deployment’s name.
brand carries your organization’s public brand overrides so the widget can render in your colours without a custom build. It is sparse: it contains only the fields your organization has set, and is {} when none are. Documentation, support and legal links are never included. See Branding.
When a request is refused, the response carries no Access-Control-Allow-Origin header. In a cross-origin browser request, fetch therefore rejects with a network error instead of exposing the error body. An unknown, malformed, revoked or expired widget key all return the same 401.
string
required
The deployment’s public widget key,
arukz_wk_…. An arukz_sk_ API key is not accepted here.string
required
Set by the browser. It must exactly match an origin allowed for this deployment. When you call
from outside a browser, set it yourself.
Response
string
required
Always
active.object
required
Your organization’s public brand overrides, in camelCase. Every section and field is optional.
Last modified on September 27, 2026