- Chinese FAQ: https://kokonna.art/zh-hans/pages/常见问问题
- OpenAPI: https://kokonna.art/pages/openapi
Official product materials list calendar/local weather, word of the day, traditional almanac, global travel recommendations and daily news. FAQ also lists image rotation and AI art modes (voice, text, sketch, photo style transformation). These product/widget categories are not a verified complete catalog of current mainland WeChat mini-program subscriptions. The user's daily-poetry subscription is firsthand evidence of that option; public materials reviewed do not document its subscription contract.
The current OpenAPI documents device, upload, listImages, deleteImage, image retrieval, displayImageById and displayImageByName. Device metadata includes rotation mode/interval and current image/cover; it does not document selected subscription IDs or original template data. No subscription catalog/read/create/update/cancel interface is listed. Therefore an official subscription integration is blocked on a documented provider contract, not on a Frame Flow rendering limitation.
Frame Flow displays official categories and explicit unsupported status, with links to original docs. It does not present its own poetry provider as the official subscription, fabricate endpoints, infer subscription from an image, or alter existing official subscriptions. A future documented API should be implemented in the KoKonna driver, preserving the public capability model, rather than through vendor-specific core behavior.
To complete official integration: obtain a current mini-program subscription-page screenshot/catalog and official subscription API documentation (endpoint, auth type, schema, effect of writes). Credentials or session tokens must not appear in screenshots or documentation. No private endpoint guesses or authenticated cloud writes were used in this investigation.
## Follow-up: widgets versus public API (2026-10-02)
Further investigation after the user confirmed the mini-program can read the selected widget:
- Official usage guide https://kokonna.art/pages/how-to-use calls these **Smart Widgets**. Step 04 describes selecting Weather, News or Calendars and automatic midnight refresh. This confirms official selection/refresh functionality; it does not document the underlying request paths or authentication.
- Manufacturer site https://www.galaxyguide.cn/ confirms weather/calendar widgets and slideshows.
- Additional reference https://kokonna.art/zh-hans/pages/openapi_cn fetched HTTP 200. Its documented device/image endpoints contain no widget/subscription configuration contract.
- GitHub `patrickchen914/kokonna`, inspected `custom_components/kokonna/const.py`, `__init__.py`, `select.py`: uses galaxyguide OpenAPI gallery/image switching. No widget configuration implementation found in these files.
- GitHub `nixihz/kokonna-skill`, inspected `kokonna/client.py` and README: exposes public image/device endpoints; no widget/subscription calls found.
- NPM lookup for `@guooscar/kokonna-frame` returned HTTP 404 during this follow-up; it cannot provide current independently retrievable endpoint evidence. Earlier protocol-reference findings remain historical.
**Correct interpretation:** public API documentation does not list widget/subscription configuration endpoints. This is not evidence that the official client lacks internal APIs. Since the mini-program displays selected configuration, some official client/backend mechanism provides it; a separate authenticated internal API is plausible but remains an inference. No actual widget endpoint name, HTTP method, request/response schema or authorization model has yet been verified. Do not label the integration impossible merely because it is undocumented.
Next verification should observe the user's own authorized mini-program read requests when opening widget selection/current-widget settings. Capture only the necessary request path, method and sanitized JSON; do not export login tokens, cookies or full network archives. Begin with read-only inspection and keep subscription mutations separate. The public device API key must not be assumed equivalent to mini-program user authentication.
