/segmentfault/questions/related

POST /api/segmentfault/questions/related

Price: 1 credit

List the questions SegmentFault shows as related to a question, each with title, excerpt, tags, view and answer counts and the accepted answer id

How to use it

The related list is short and fixed by SegmentFault, so it can hold fewer questions than `count`.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• question string required — SegmentFault question id or question URL (examples: "1010000048328093", "https://segmentfault.com/q/1010000048328093")
• count integer required — Max number of related questions to return (min: 1)

Response

• @type string (default: "SegmentfaultRelatedQuestion")
• id string required
• url string nullable
• excerpt string nullable
• view_count integer nullable
• answer_count integer nullable
• accepted_answer_id string nullable
• tags array (default: [])
  • @type string (default: "SegmentfaultTag")
  • id string nullable
  • name string required
  • url string nullable
  • description string nullable
  • image string nullable
  • icon string nullable
  • content_count integer nullable
  • popularity_score 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.