CourtListener · Authentication Profile

Court Listener Authentication

Authentication

CourtListener secures its APIs with apiKey and http across 3 declared security schemes, as derived from its OpenAPI definitions.

LegalCourt DataCase LawPACERJudicialCitationsOral ArgumentsFederal CourtsState CourtsOpen Data
Methods: apiKey, http Schemes: 3 OAuth flows: API key in: cookie, header

Security Schemes

tokenAuth apiKey
· in: header (Authorization)
basicAuth http
scheme: basic
cookieAuth apiKey
· in: cookie (sessionid)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/court-listener-openapi.json
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - cookie
  - header
schemes:
- name: tokenAuth
  type: apiKey
  in: header
  parameter: Authorization
  description: 'Token-based authentication. Format: ''Token <your_token>'''
  sources:
  - openapi/court-listener-openapi.json
- name: basicAuth
  type: http
  scheme: basic
  sources:
  - openapi/court-listener-openapi.json
- name: cookieAuth
  type: apiKey
  in: cookie
  parameter: sessionid
  sources:
  - openapi/court-listener-openapi.json