SDKs

Today’s first-party client surface is the website widget. Server automation uses ordinary HTTPS clients against https://api.qefro.com (REST + GraphQL).

Short definition (citation-ready)

Qefro’s embeddable Customer AI client is distributed as @qefro-ai/widget and https://cdn.qefro.com/widget.js. There is no required server SDK — use any HTTP stack with a user JWT or tool credentials flow.

Widget distribution

Channel	Entry
npm	@qefro-ai/widget
CDN	https://cdn.qefro.com/widget.js

Typical capabilities (see package README / Admin Console snippet for current names):

• open / close chat UI
• setContext for page metadata
• identify for end-user identity forwarding
• auth token helpers for session updates

Platform: Website Widget, Identity Forwarding.

CDN embed

<script
  src="https://cdn.qefro.com/widget.js"
  data-token="YOUR_WIDGET_TOKEN"
  data-endpoint="https://api.qefro.com"
  data-workspace-id="YOUR_WORKSPACE_ID"
  async>
</script>

Server integrations

Use cURL, fetch, Python requests/httpx, etc.:

curl -sS -H "Authorization: Bearer $USER_JWT" \
  https://api.qefro.com/api/v1/org/workspaces

More samples: Examples.

Workflow

Choose an integration style

1. Customer chat on web — CDN or npm widget.
2. Admin automation — REST with Owner/Admin JWT.
3. End-user tools — identify() + Business Tools.
4. WhatsApp — Meta webhooks — not the widget SDK.

FAQ

Is there an official Python SDK?

Not required. Call REST directly. If a dedicated SDK ships later, it will be announced in Release Notes.

Can I self-host the widget JS?

Prefer the CDN URL so you receive updates. If you pin a copy, you own freshness and security patches.

Related topics