live-chat

GET /v1/chat/widgets/{widgetId}

One chat's settings and its AI allowance.

All live-chat endpoints

Authentication

Send an API key as a bearer token. The key must carry the livechat.view permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X GET https://api.zinndigital.com/v1/chat/widgets/{widgetId} \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Requires `livechat.view` or `livechat.manage`.

Parameters

NameTypeRequiredWhat it is
widgetId (path)stringYes

Response

NameTypeRequiredWhat it is
idstringYes
site_idstringYes
namestringYes
public_keystringYes
enabledbooleanYesWhether the chat renders. Created FALSE always: the plugin ships in the deploy footprint of every WordPress site we host, so a widget may exist for a customer who never asked fo…
allowed_originsstring[]YesOrigins the widget may be embedded on. An EMPTY list refuses every page rather than allowing any — this is the only control stopping somebody else's site opening conversations a…
tierstringYes
greetingstringYes
team_namestringYes
accent_colourstringYes
positionstring<left, right>Yes
hide_brandingbooleanYes
ai_enabledbooleanYes
offline_emailstringYes
business_hoursobjectNo
open_nowbooleanYes
ai_allowanceChatAiAllowanceYes
limitsobjectYes
premium_extra_codestringYesThe catalogue code to buy for the premium tier.

Errors this endpoint can return

401 · 403 · 404