/csdn/questions

POST /api/csdn/questions

Price: 20 credits

Get one CSDN Q&A question by id or URL: title, body as HTML and text, tags, asker, view, like and answer counts, and every answer with its author, body and votes

How to use it

Question ids come from csdn/questions/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• question string required — CSDN Q&A question id or URL (examples: "8125663", "https://ask.csdn.net/questions/8125663")

Response

• @type string (default: "CsdnQuestion")
• id string required
• url string nullable
• body_html string nullable
• body_text string nullable
• answer_count integer nullable
• view_count integer nullable
• like_count integer nullable
• best_answer_id string nullable
• is_essence boolean nullable
• is_answer_accepted boolean nullable
• is_closed boolean nullable
• effective_answer_count integer nullable
• asker_answered_question_count integer nullable
• asker_accepted_answer_count integer nullable
• source string nullable
• tags array (default: [])
• categories array (default: [])
• author_alias string nullable
• author_name string nullable
• author_image string nullable
• author_url string nullable
• created_at integer nullable
• updated_at integer nullable
• answers array (default: [])
  • @type string (default: "CsdnAnswer")
  • id string required
  • body_html string nullable
  • body_text string nullable
  • like_count integer nullable
  • dislike_count integer nullable
  • is_best boolean nullable
  • is_edited boolean nullable
  • author_alias string nullable
  • author_name string nullable
  • author_image string nullable
  • author_url string nullable
  • author_certification string nullable
  • created_at integer nullable
  • updated_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 question with that id 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.