POST /api/courtlistener/judges
Price: 1 credit
Get a US judge with biography, judicial positions, schools, ABA ratings and party affiliation
Get a single US judge (person) by CourtListener id. Returns full name, alternate names, gender, race, religion, birth and death dates, birth city and state, FJC id, judicial and other positions (court, appointer, predecessor, supervisor, selection method, nomination/confirmation/start/termination dates), schools attended, ABA ratings and political-party affiliations.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)judge integer required — Judge (person) identifier (examples: 65, 1211)@type string (default: "CourtlistenerJudge")id integer requiredname string nullablealias string nullablealiases array (default: [])alias_ids array (default: [])gender string nullablereligion string nullableraces array (default: [])fjc_id integer nullableborn_at integer nullabledied_at integer nullabledob_city string nullabledob_state string nullablepositions array (default: [])@type string (default: "CourtlistenerJudgePosition")position_type string nullablejob_title string nullableorganization_name string nullablecourt_id string nullableappointer string nullablepredecessor string nullablesupervisor string nullableselection_method string nullablenomination_process string nullabletermination_reason string nullablenominated_at integer nullableelected_at integer nullableconfirmed_at integer nullablestart_at integer nullableterminated_at integer nullableretired_at integer nullableeducations array (default: [])@type string (default: "CourtlistenerJudgeEducation")school_name string nullableaba_ratings array (default: [])@type string (default: "CourtlistenerAbaRating")rating string nullablepolitical_affiliations array (default: [])@type string (default: "CourtlistenerPoliticalAffiliation")political_party string nullableweb_url string nullable422 — 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 — Judge not found 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.