/csdn/communities

POST /api/csdn/communities

Price: 10 credits

Get one CSDN community (bbs.csdn.net forum) by slug or URL: name, description, location, member, topic and follower counts, owner, sections and its latest topics with view, comment and like counts

How to use it

`latest_topics` holds the first page the community shows, up to 10 topics.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• community string required — CSDN community (bbs.csdn.net forum) slug or URL (examples: "ecological-developer", "https://bbs.csdn.net/forums/ecological-developer")

Response

• @type string (default: "CsdnCommunity")
• id string required
• alias string nullable
• url string nullable
• name string nullable
• description string nullable
• image string nullable
• province string nullable
• district string nullable
• member_count integer nullable
• topic_count integer nullable
• follower_count integer nullable
• owner_alias string nullable
• owner_name string nullable
• sections array (default: [])
• created_at integer nullable
• latest_topics array (default: [])
  • @type string (default: "CsdnTopic")
  • id string required
  • url string nullable
  • description string nullable
  • cover string nullable
  • section string nullable
  • is_featured boolean nullable
  • is_pinned boolean nullable
  • view_count integer nullable
  • comment_count integer nullable
  • like_count integer nullable
  • bookmark_count integer nullable
  • average_score number nullable
  • author_alias string nullable
  • author_name string nullable
  • author_image string nullable
  • author_url string nullable
  • created_at integer nullable
  • updated_at integer nullable
  • last_reply_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 community with that slug 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.