Widget config API

Reads and writes the project's widget configuration. Updates bust the edge cache immediately so changes appear on the embedded widget within seconds.

Endpoints

Get config

bash
curl https://api.rogeriq.com/api/v1/projects/prj_xxx/widget/config \  -H "X-API-Key: riq_xxx"

bash
rogeriq widget config

ts
const config = await roger.widget.getConfig();

Response

json
{  "data": {    "project_id": "prj_xxx",    "enabled": true,    "position": "bottom-right",    "color": "#F26B3A",    "welcome_message": "Hi! How can we help?",    "show_branding": true,    "theme": "light",    "locale": "en",    "...": "more provider-specific fields"  }}

The response is open-ended — any new widget field added in future releases will appear here without an SDK upgrade.

Update config

bash
curl -X PATCH https://api.rogeriq.com/api/v1/projects/prj_xxx/widget/config \  -H "X-API-Key: riq_xxx" \  -H "Content-Type: application/json" \  -d '{"theme": "dark", "color": "#5b21b6", "welcome_message": "Need help?"}'

bash
rogeriq widget set --theme dark --primary-color '#5b21b6' --welcome-message "Need help?"

ts
await roger.widget.updateConfig({  theme: "dark",  color: "#5b21b6",  welcome_message: "Need help?",});

Common fields

The widget supports many more fields (operating hours, secure mode, custom CSS, etc). They all accept partial updates — only include fields you want to change.

Cache behavior

The widget runtime reads its config from an edge cache keyed by project id. On every successful PATCH, the cache key widget-config:{pid} is deleted server-side so the next widget load (within seconds) sees the new values.