/courtlistener/financial-disclosures/search

POST /api/courtlistener/financial-disclosures/search

Price: 1 credit

List judicial financial disclosures, optionally filtered by judge

How to use it

List judicial financial disclosures on CourtListener, optionally filtered by judge (person id). Returns disclosure metadata (filing year, report type, source PDF, page count); fetch a single disclosure by id to get the full extracted investment, gift, debt and income records.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• person integer nullable — Filter by judge (person) id whose disclosures to list (examples: 384)
• count integer required — Number of disclosures to return (min: 1)

Response

• @type string (default: "CourtlistenerFinancialDisclosure")
• id integer required
• person_id string nullable
• year integer nullable
• report_type integer nullable
• page_count integer nullable
• document_url string nullable
• thumbnail string nullable
• sha1 string nullable
• is_amended boolean (default: false)
• addendum string nullable
• addendum_redacted boolean (default: false)
• has_been_extracted boolean (default: false)
• agreements array (default: [])
  • @type string (default: "CourtlistenerFdAgreement")
  • id integer required
  • date_raw string nullable
  • parties_and_terms string nullable
  • redacted boolean (default: false)
• debts array (default: [])
  • @type string (default: "CourtlistenerFdDebt")
  • id integer required
  • creditor_name string nullable
  • description string nullable
  • value_code string nullable
  • redacted boolean (default: false)
• gifts array (default: [])
  • @type string (default: "CourtlistenerFdGift")
  • id integer required
  • source string nullable
  • description string nullable
  • value string nullable
  • redacted boolean (default: false)
• investments array (default: [])
  • @type string (default: "CourtlistenerFdInvestment")
  • id integer required
  • description string nullable
  • page_number integer nullable
  • gross_value_code string nullable
  • gross_value_method string nullable
  • income_code string nullable
  • income_type string nullable
  • transaction_type string nullable
  • transaction_date_raw string nullable
  • transaction_value_code string nullable
  • transaction_gain_code string nullable
  • transaction_partner string nullable
  • redacted boolean (default: false)
  • transaction_at integer nullable
• non_investment_incomes array (default: [])
  • @type string (default: "CourtlistenerFdNonInvestmentIncome")
  • id integer required
  • date_raw string nullable
  • source_type string nullable
  • income_amount string nullable
  • redacted boolean (default: false)
• positions array (default: [])
  • @type string (default: "CourtlistenerFdPosition")
  • id integer required
  • position string nullable
  • organization_name string nullable
  • redacted boolean (default: false)
• reimbursements array (default: [])
  • @type string (default: "CourtlistenerFdReimbursement")
  • id integer required
  • source string nullable
  • date_raw string nullable
  • location string nullable
  • purpose string nullable
  • items_paid_or_provided string nullable
  • redacted boolean (default: false)
• spouse_incomes array (default: [])
  • @type string (default: "CourtlistenerFdSpouseIncome")
  • id integer required
  • source_type string nullable
  • date_raw string nullable
  • redacted boolean (default: false)
• 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 — The entity was not found, or a precondition failed 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.