/courtlistener/judges

POST /api/courtlistener/judges

Price: 1 credit

Get a US judge with biography, judicial positions, education, ABA ratings and party affiliation

How to use it

Get a single US judge (person) by CourtListener id. Returns full name and name parts, gender, race, religion, birth and death dates and places, FJC id, campaign-finance total received, judicial positions (court, appointer, predecessor and supervisor ids, selection method, nomination/confirmation/start/termination dates, confirmation votes), education (schools and degrees), ABA ratings and political-party affiliations.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• judge integer required — Judge (person) identifier (examples: 65, 1211)

Response

• @type string (default: "CourtlistenerJudge")
• id integer required
• name string nullable
• alias string nullable
• name_first string nullable
• name_middle string nullable
• name_last string nullable
• name_suffix string nullable
• gender string nullable
• religion string nullable
• races array (default: [])
• fjc_id integer nullable
• ftm_total_received number nullable
• has_photo boolean (default: false)
• born_at integer nullable
• died_at integer nullable
• dob_city string nullable
• dob_state string nullable
• dob_country string nullable
• dod_city string nullable
• dod_state string nullable
• dod_country string nullable
• positions array (default: [])
  • @type string (default: "CourtlistenerJudgePosition")
  • id integer required
  • position_type string nullable
  • job_title string nullable
  • organization_name string nullable
  • court_id string nullable
  • appointer_id string nullable
  • predecessor_id string nullable
  • supervisor_id string nullable
  • location_city string nullable
  • location_state string nullable
  • selection_method string nullable
  • nomination_process string nullable
  • termination_reason string nullable
  • votes_yes integer nullable
  • votes_no integer nullable
  • votes_yes_percent number nullable
  • votes_no_percent number nullable
  • nominated_at integer nullable
  • elected_at integer nullable
  • confirmed_at integer nullable
  • start_at integer nullable
  • terminated_at integer nullable
  • retired_at integer nullable
• educations array (default: [])
  • @type string (default: "CourtlistenerJudgeEducation")
  • id integer required
  • school_name string nullable
  • degree_level string nullable
  • degree_detail string nullable
  • degree_year integer nullable
• aba_ratings array (default: [])
  • @type string (default: "CourtlistenerAbaRating")
  • year_rated integer nullable
  • rating string nullable
• political_affiliations array (default: [])
  • @type string (default: "CourtlistenerPoliticalAffiliation")
  • political_party string nullable
  • source string nullable
  • start_at integer nullable
  • end_at integer nullable
• web_url string nullable
• created_at integer nullable
• updated_at 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 — 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.

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.