WeChat Official Accounts Article Comments

Use this focused JustOneAPI skill for article Comments in WeChat Official Accounts. It targets GET /api/weixin/get-article-comment/v1. Required non-token inputs are articleUrl. OpenAPI describes it as: Get WeChat Official Accounts article Comments data, including commenter details, comment text, and timestamps, for feedback analysis.

Endpoint Scope

• Platform key: weixin
• Endpoint key: get-article-comment
• Platform family: WeChat Official Accounts
• Skill slug: justoneapi-weixin-get-article-comment

| Operation | Version | Method | Path | OpenAPI summary | | --- | --- | --- | --- | --- | | getArticleComment | v1 | GET | /api/weixin/get-article-comment/v1 | Article Comments |

Inputs

| Parameter | In | Required by | Optional by | Type | Notes | | --- | --- | --- | --- | --- | --- | | articleUrl | query | all | n/a | string | The URL of the Weixin article |

Request body: none documented; send parameters through path or query arguments.

Version Choice

Use getArticleComment for the documented v1 endpoint. There are no alternate versions grouped in this skill.

Run This Endpoint

Supported operation IDs in this skill: getArticleComment.

node {baseDir}/bin/run.mjs --operation "getArticleComment" --token "$JUST_ONE_API_TOKEN" --params-json '{"articleUrl":"<articleUrl>"}'

Ask for any missing required parameter before calling the helper. Keep user-provided IDs, cursors, keywords, and filters unchanged.

Environment

• Required: JUST_ONE_API_TOKEN
• Pass the token with --token "$JUST_ONE_API_TOKEN"; do not paste token values into chat messages, screenshots, or logs.
• Get a token from Just One API Dashboard.
• Authentication details: Just One API Usage Guide.

Output Focus

• State the operation ID and endpoint path used, for example getArticleComment on /api/weixin/get-article-comment/v1.
• Echo the required lookup scope (articleUrl) before summarizing results.
• Prioritize fields that support this endpoint purpose: Get WeChat Official Accounts article Comments data, including commenter details, comment text, and timestamps, for feedback analysis.
• Return raw JSON only after the short, endpoint-specific summary.
• If the backend errors, include the backend payload and the exact operation ID.