/ratemyprofessors/professors/reviews

POST /api/ratemyprofessors/professors/reviews

Price: 10 credits

List student reviews of a Rate My Professors professor, newest first

How to use it

List the individual student reviews of one professor, with per-review ratings, course, grade and tags. Narrow to one course with a code taken from the `courses` of ratemyprofessors/professors.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• professor string required — Professor id or profile URL (examples: "1787414", "https://www.ratemyprofessors.com/professor/1787414")
• count integer required — Max number of results (min: 1)
• course string nullable — Only reviews for this course code, as listed in the professor's `courses` (examples: "EEB390")

Response

• @type string (default: "RatemyprofessorsProfessorReview")
• id string required
• professor_id string required
• created_at integer nullable
• course string nullable
• text string nullable
• quality_rating integer nullable
• clarity_rating integer nullable
• helpful_rating integer nullable
• difficulty_rating integer nullable
• grade string nullable
• is_attendance_mandatory boolean nullable
• is_would_take_again boolean nullable
• textbook_use integer nullable
• is_textbook_used boolean nullable
• course_type integer nullable
• is_online_class boolean nullable
• is_for_credit boolean nullable
• tags array (default: [])
• thumbs_up_count integer nullable
• thumbs_down_count integer nullable
• flag_status string nullable
• admin_reviewed_at integer nullable

Errors

• 422 — The professor has no ratings for the given course 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 professor exists 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.