Zhihu user pins API
A Zhihu user's pins
Use the Zhihu user pins API to read public Zhihu user_pins. A Zhihu user's pins.
Request
Send your API key as a Bearer token. Replace YOUR_API_KEY with a key from your console.
curl "https://xtikapi.com/v1/zhihu/user_pins/list?user_url_token=example" \
-H "Authorization: Bearer YOUR_API_KEY"import requests
response = requests.get(
"https://xtikapi.com/v1/zhihu/user_pins/list",
params={"user_url_token":"example"},
headers={"Authorization": "Bearer YOUR_API_KEY"},
)
print(response.json())const response = await fetch("https://xtikapi.com/v1/zhihu/user_pins/list?user_url_token=example", {
headers: { Authorization: "Bearer YOUR_API_KEY" },
});
console.log(await response.json());Parameters
| Name | Type | Required |
|---|---|---|
| user_url_token | string | required |
| cursor | string | optional |
| limit | string | optional |
Response fields
Every platform returns the same post shape. A field the platform does not provide is named in meta.unavailable.
- id
- url
- text
- author
- createdAt
- likeCount
- commentCount
- shareCount
- viewCount
- cover
Example response
A sample payload that shows the shape. Values are made up.
{
"example": true,
"data": {
"items": [
{
"id": "example-post",
"url": "https://example.com/post/example",
"text": "Example post",
"author": {
"id": "example-user",
"username": "example"
},
"createdAt": "2026-01-01T00:00:00Z",
"likeCount": 1
}
]
},
"meta": {
"request_id": "example",
"endpoint": "zhihu.user_pins.list",
"normalized": true,
"unavailable": [],
"billing": {
"charged": true,
"amount": 0.002,
"balance": 4.98
}
}
}Error codes
Errors are not billed. Retry the ones marked yes. More in the API quickstart.
| Code | HTTP | Retry | Meaning |
|---|---|---|---|
| unauthorized | 401 | no | API key is missing, invalid, or revoked. |
| rate_limited | 429 | yes | Too many requests. |
| invalid_params | 422 | no | Request parameters are invalid. |
| price_exceeds_max | 402 | no | This call costs more than X-Max-Price. |
| insufficient_balance | 402 | no | Balance is too low for this call. |
| key_limit_reached | 402 | no | This API key has reached its spend limit. |
| idempotency_conflict | 409 | no | This Idempotency-Key was already used with different parameters. |
| idempotency_in_progress | 409 | yes | A request with this Idempotency-Key is still running. |
| response_too_large | 409 | no | The response is too large to store for a safe retry. |
| upstream_error | 502 | yes | The data provider returned an error. You were not charged. |
| upstream_timeout | 504 | yes | The data provider timed out. You were not charged. |
| internal_error | 500 | yes | Something went wrong on our side. You were not charged. |
| not_found | 404 | no | No such endpoint. |
More Zhihu APIs
- Zhihu article search API→
- Zhihu answer details API→
- Zhihu account details API→
- Zhihu answer comments API→
- Zhihu comment replies API→
- Zhihu question details API→
- Zhihu question answers API→
- Zhihu article details API→
- Zhihu column articles API→
- Zhihu pin details API→
- Zhihu user answers API→
- Zhihu user articles API→
- Zhihu account search API→
- Zhihu account followers API→
- Zhihu hot list API→
Questions
What does the Zhihu user pins API return?
A post object with the fields listed on this page. Missing provider fields are named in meta.unavailable.
When is the Zhihu user pins API billed?
This call costs $0.002 when the provider returns HTTP 200. An empty result is billed. Errors and timeouts are not billed.
What do I do if the provider returns an error?
The response has charged set to false. Read the error code and retry if the error says retry is true. Your balance is unchanged.
Where is this resource on another platform?
Use the links on this page for the same resource and action on other platforms. Change the platform word in the path.