Pugongying creator follower quality API
Follower quality summary of a Pugongying creator: active share, growth
Use the Pugongying creator follower quality API to read public Pugongying creators. Follower quality summary of a Pugongying creator: active share, growth.
Request
Send your API key as a Bearer token. Replace YOUR_API_KEY with a key from your console.
curl -X POST "https://xtikapi.com/v1/pugongying/creators/follower_summary" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"id":"1234567890"}'import requests
response = requests.post(
"https://xtikapi.com/v1/pugongying/creators/follower_summary",
json={"id":"1234567890"},
headers={"Authorization": "Bearer YOUR_API_KEY"},
)
print(response.json())const response = await fetch("https://xtikapi.com/v1/pugongying/creators/follower_summary", {
method: "POST",
headers: {
Authorization: "Bearer YOUR_API_KEY",
"Content-Type": "application/json",
},
body: JSON.stringify({"id":"1234567890"}),
});
console.log(await response.json());Parameters
| Name | Type | Required |
|---|---|---|
| id | string | required |
Response fields
data holds the fields exactly as the platform sends them, and meta.normalized is false. meta still carries the request ID and what was billed.
Example response
Recorded from a live call on 2026-11-18. Names, text, links and images are replaced with examples; counts, dates and field names are real.
{
"data": {
"code": 0,
"msg": "Example text",
"guid": null,
"success": true,
"data": {
"fansNum": 56594,
"fansIncreaseNum": 619,
"fansGrowthRate": "Example text",
"fansGrowthBeyondRate": "Example text",
"activeFansL28": 0,
"activeFansRate": "Example text",
"activeFansBeyondRate": "Example text",
"engageFansRate": "Example text",
"engageFansL30": 0,
"engageFansBeyondRate": "Example text",
"readFansIn30": 0,
"readFansRate": "Example text",
"readFansBeyondRate": "Example text",
"payFansUserRate30d": "Example text",
"payFansUserNum30d": 15035
}
},
"meta": {
"request_id": "example",
"endpoint": "pugongying.creators.follower_summary",
"normalized": false,
"unavailable": [],
"billing": {
"charged": true,
"amount": 0.04,
"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 Pugongying APIs
- Pugongying creator search API→
- Pugongying creator details API→
- Pugongying creator audience API→
- Pugongying creator metrics API→
- Pugongying creator notes API→
- Pugongying similar creators API→
- Pugongying creator follower growth API→
- Pugongying creator cost summary API→
- Pugongying creator data history API→
- Pugongying note metrics API→
- Pugongying trending notes API→
- Pugongying keyword search index API→
- Pugongying related keywords API→
- Pugongying keyword overview API→
Questions
What does the Pugongying creator follower quality API return?
A record object with the fields listed on this page. Missing provider fields are named in meta.unavailable.
When is the Pugongying creator follower quality API billed?
This call costs $0.04 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.