Zhihu Article comment settings API
API health
- 24h health
- Normal
- Healthy / normal
- Available
Last 24 hours
Last 30 days
Read the comment settings a signed-out visitor sees on one Zhihu article: whether replies are open, the comment box hint and the picture limit. Zhihu returns the same settings for any article ID, so this cannot tell you whether an article exists.
Send POST https://api.everyinfra.com/api/v1/social with platform set to zhihu and action set to article_comment_config. Price $0.56 per 1,000 requests ($0.000556 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
AI prompt
#Please help me write a data collection script with the EveryInfra Zhihu Article comment settings endpoint (zhihu/article_comment_config).
How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to zhihu and action to article_comment_config, and put the parameters inside params.
- Required parameters:
- url: A Zhihu article link (https://zhuanlan.zhihu.com/p/<article ID>) or the numeric article ID.
- Returns one object. Main fields: id, url, can_reply, can_segment_reply, is_anonymous, input_placeholder, picture_max_count.
- Example request body:
{
"platform": "zhihu",
"action": "article_comment_config",
"params": {
"url": "https://zhuanlan.zhihu.com/p/2032860336215307118"
}
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
#| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | zhihu | Platform identifier, fixed value. |
action | body | string | Yes | article_comment_config | Capability identifier, fixed value. |
url | body.params | string | Yes | - | A Zhihu article link (https://zhuanlan.zhihu.com/p/<article ID>) or the numeric article ID. |
Code samples
#curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "zhihu",
"action": "article_comment_config",
"params": {
"url": "https://zhuanlan.zhihu.com/p/2032860336215307118"
}
}'OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
#{ "id": "req_…", "platform": "zhihu", "action": "article_comment_config", "results": { "id": "2032860336215307118", "url": "https://zhuanlan.zhihu.com/p/2032860336215307118", "can_reply": false, "can_segment_reply": false, "is_anonymous": true, "input_placeholder": "未登录用户", "picture_max_count": 1, "platform": "zhihu" }, "billing": { "charged": …, "charged_usd": …, "balance_after_usd": …, … }, "quota": { … }}
Response fields
#Business data is in results. The table lists the fields a record can contain. Values the platform does not show are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
url | Link to the record on the platform. |
can_reply | Keeps the platform's own meaning |
can_segment_reply | Keeps the platform's own meaning |
is_anonymous | Keeps the platform's own meaning |
input_placeholder | Keeps the platform's own meaning |
picture_max_count | Keeps the platform's own meaning |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
Errors and billing
#- 401
- Missing or invalid key.
- 402
- Insufficient balance. Top up first.
- 422
- Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
- 429
- Per-minute request limit reached. Wait for Retry-After, then try again.
- 503
- Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
- 200 empty
- No data. No charge.