/coursehero/documents

POST /api/coursehero/documents

Price: 10 credits

Get a Course Hero study document by id or URL

How to use it

Get one Course Hero document by numeric id or /file/ URL: its metadata, school, department and course, ratings and the text of the pages open without an account.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• document string required — Course Hero document id or document URL. (examples: "202543466", "https://www.coursehero.com/file/202543466/focus-on-nursing-pharmacology-8th-edition-test-bank-by-amy-karch-chapter-1-59-complete-guide-2022pd/"; minLength: 1)

Response

• @type string (default: "CourseheroDocument")
• id string required
• alias string nullable
• name string required
• file_name string nullable
• summary string nullable
• url string required
• language string nullable
• keywords array (default: [])
• published_at integer nullable
• updated_at integer nullable
• page_count integer nullable
• rating_value number nullable
• rating_count integer nullable
• helpful_percentage number nullable
• is_free boolean nullable
• text string nullable
• school object nullable
  • @type string (default: "CourseheroTaxonomyRef")
  • id string required
  • name string nullable
  • url string nullable
• department object nullable
  • @type string (default: "CourseheroTaxonomyRef")
  • id string required
  • name string nullable
  • url string nullable
• course object nullable
  • @type string (default: "CourseheroTaxonomyRef")
  • id string required
  • name string nullable
  • url string nullable
• author object nullable
  • @type string (default: "CourseheroAuthor")
  • alias string required
  • url string required

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 document 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.