/coursehero/questions

POST /api/coursehero/questions

Price: 20 credits

Get a Course Hero tutor question by id or URL

How to use it

Get one Course Hero tutor question by numeric id or /tutors-problems/ URL: the question text, subject, dates and answer count. The answer body is locked for guests and is not returned.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• question string required — Course Hero tutor question id or question URL. (examples: "8724850", "https://www.coursehero.com/tutors-problems/Algebra/8724850-need-homework-help-1Using-the-pencil-plot-the-point-6-3-2-Gra/"; minLength: 1)

Response

• @type string (default: "CourseheroQuestion")
• id string required
• url string required
• subject string nullable
• name string required
• text string nullable
• created_date string nullable
• published_date string nullable
• answer_count integer nullable
• author_name string nullable
• is_free boolean nullable
• accepted_answer object nullable
  • @type string (default: "CourseheroAnswerInfo")
  • created_date string nullable
  • upvote_count integer nullable
  • author_name string nullable
• breadcrumbs array (default: [])
  • @type string (default: "CourseheroBreadcrumb")
  • position integer required
  • name string required
  • url string 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 this 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.