Zhihu Article upvote line API
POST
API health
- 24h health
- Normal
- Healthy / normal
- Available
Normal
Last 24 hours
Last 30 days
Read the line on one Zhihu article page that says how many people upvoted it, worded as Zhihu shows it.
Send POST https://api.everyinfra.com/api/v1/social with platform set to zhihu and action set to article_relationship. 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 upvote line endpoint (zhihu/article_relationship).
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_relationship, 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, type, text.
- Example request body:
{
"platform": "zhihu",
"action": "article_relationship",
"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_relationship | 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
#bash
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_relationship",
"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
#Captured November 21, 2026 at 07:25 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed. id, billing and quota differ on every call, so only their shape is shown.
json
{ "id": "req_…", "platform": "zhihu", "action": "article_relationship", "results": { "id": "2032860336215307118", "url": "https://zhuanlan.zhihu.com/p/2032860336215307118", "type": "reaction_endorse", "text": "147 人赞同了该文章", "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. |
type | Record type; values depend on the capability (for example video / image / text). |
text | Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so). |
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.