/ratemyprofessors/professors/search

POST /api/ratemyprofessors/professors/search

Price: 20 credits

Search Rate My Professors professors by name, school and department

How to use it

Find professors on Rate My Professors by name, optionally inside one school and one of its departments. Leave the name empty with a school to list that school's professors. Pass a returned id to ratemyprofessors/professors for the full profile.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of results (min: 1; max: 10000)
• query string — Professor name to search for; empty lists every professor in scope (default: ""; examples: "smith")
• school string nullable — Only professors of this school, by school id or school page URL (examples: "1258", "https://www.ratemyprofessors.com/school/1258")
• department_id string nullable — Only professors of this department, an id from the `departments` of ratemyprofessors/schools (examples: "562"; pattern: ^\d+$)

Response

• @type string (default: "RatemyprofessorsProfessorSearchItem")
• id string required
• url string required
• first_name string nullable
• last_name string nullable
• department 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
• rating_count 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 — The school or department id does not exist 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.