/csdn/users

POST /api/csdn/users

Price: 10 credits

Get one CSDN blogger by username or blog URL: name, introduction, level, IP region, follower and following counts, total views, article, download and question counts, medals and their columns

How to use it

Their articles come from csdn/users/articles.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — CSDN username or blog URL (examples: "zhulinniao", "https://blog.csdn.net/zhulinniao")

Response

• @type string (default: "CsdnUser")
• alias string required
• name string nullable
• url string nullable
• image string nullable
• introduction string nullable
• blog_title string nullable
• blog_subtitle string nullable
• level integer nullable
• code_age_years integer nullable
• ip_location string nullable
• school string nullable
• company string nullable
• is_vip boolean nullable
• original_article_count integer nullable
• follower_count integer nullable
• following_count integer nullable
• loyal_follower_count integer nullable
• total_view_count integer nullable
• rank integer nullable
• influence_level integer nullable
• influence_score integer nullable
• influence_previous_score integer nullable
• is_reward_enabled boolean nullable
• likes_received integer nullable
• comments_received integer nullable
• bookmarks_received integer nullable
• titles array (default: [])
• article_count integer nullable
• column_count integer nullable
• download_count integer nullable
• question_count integer nullable
• forum_post_count integer nullable
• video_count integer nullable
• blink_count integer nullable
• course_count integer nullable
• live_count integer nullable
• community_count integer nullable
• interests array (default: [])
• medals array (default: [])
  • @type string (default: "CsdnMedal")
  • id string required
  • name string nullable
  • description string nullable
  • image string nullable
• columns array (default: [])
  • @type string (default: "CsdnColumn")
  • id string required
  • url string nullable
  • description string nullable
  • image string nullable
  • article_count integer nullable
  • is_free boolean nullable
  • created_at integer nullable
  • updated_at integer nullable
• registered_at integer nullable
• blog_created_at integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No user with that username Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.