/ratemyprofessors/professors

POST /api/ratemyprofessors/professors

Price: 1 credit

Get a Rate My Professors professor profile by id or URL

How to use it

Look up one professor on Rate My Professors by the numeric id in their profile URL. Use it for the aggregate picture of a professor; the individual student reviews come from ratemyprofessors/professors/reviews, and ids come from ratemyprofessors/professors/search.

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")

Response

• @type string (default: "RatemyprofessorsProfessor")
• id string required
• url string required
• first_name string nullable
• last_name string nullable
• department string nullable
• department_id string nullable
• school object nullable
  • @type string (default: "RatemyprofessorsSchoolRef")
  • id string required
  • name string nullable
  • url string required
  • city string nullable
  • state string nullable
  • country string nullable
  • country_code string nullable
• rating number nullable
• difficulty number nullable
• would_take_again_percent number nullable
• would_take_again_count integer nullable
• rating_count integer nullable
• rating_distribution object nullable
  • @type string (default: "RatemyprofessorsRatingDistribution")
  • total_count integer nullable
  • rating_1_count integer nullable
  • rating_2_count integer nullable
  • rating_3_count integer nullable
  • rating_4_count integer nullable
  • rating_5_count integer nullable
• attendance_mandatory_counts object nullable
  • @type string (default: "RatemyprofessorsAnswerCounts")
  • yes_count integer nullable
  • no_count integer nullable
  • neither_count integer nullable
  • total_count integer nullable
• for_credit_counts object nullable
  • @type string (default: "RatemyprofessorsAnswerCounts")
  • yes_count integer nullable
  • no_count integer nullable
  • neither_count integer nullable
  • total_count integer nullable
• most_useful_review_id string nullable
• reply_count integer nullable
• replies array (default: [])
  • @type string (default: "RatemyprofessorsProfessorReply")
  • id string required
  • review_id string nullable
  • text string nullable
  • created_at integer nullable
  • updated_at integer nullable
  • flag_status string nullable
• lock_status string nullable
• courses array (default: [])
  • @type string (default: "RatemyprofessorsCourse")
  • name string required
  • rating_count integer nullable
• tags array (default: [])
  • @type string (default: "RatemyprofessorsTag")
  • id string nullable
  • name string required
  • count integer nullable
• similar_professors array (default: [])
  • @type string (default: "RatemyprofessorsSimilarProfessor")
  • id string required
  • url string required
  • first_name string nullable
  • last_name string nullable
  • rating number 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 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.