How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Lex Machina List API

Provides cannonical lists for specific fields.

Lex Machina List API is one of 21 APIs that Lex Machina publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include List. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 15 operations across 15 paths, and defines 16 schemas. It is described by OpenAPI 3.1.0, at version 20260324.

Requests are made against a single base URL, https://api.lexmachina.com.

15 operations 15 paths 16 schemas 15 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
20260324
Base URL
https://api.lexmachina.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Lex Machina List API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JwtAccessBearer).

Paths & Operations 15

Across 15 paths, the API surfaces 15 operations — 15 GET. Each is listed below with its method, path, parameters, and response codes.

List 15

Provides cannonical lists for specific fields.

GET
/list-appealability-rulings
List Appealability Rulings
list_appealability_rulings → 200401404422
GET
/list-appellate-decisions/FederalDistrict
List Appellate Decisions
list_appellate_decisions → 200401404422
GET
/list-case-resolutions/{court_type}
List Case Resolutions
list_case_resolutions 1 param → 200422401404
GET
/list-case-tags/{court_type}
List Case Tags
list_case_tags 1 param → 200422401404
GET
/list-case-types/{court_type}
List Case Types
list_case_types 1 param → 200422401404
GET
/list-courts/{court_type}
List Courts
list_courts 1 param → 200422401404
GET
/list-damages/FederalDistrict
List Federal District Damages
list_federal_district_damages → 200401404422
GET
/list-damages/State
List State Damages
list_state_damages → 200401404422
GET
/list-events/{court_type}
List Events
list_events 1 param → 200422401404
GET
/list-findings/FederalDistrict
List Federal District Findings
list_federal_district_findings → 200401404422
GET
/list-judgment-sources/FederalDistrict
List Judgment Sources
list_judgment_sources → 200401404422
GET
/list-judgment-events/State
List Judgment Events
list_judgment_events → 200401404422
GET
/list-originating-venues/FederalAppeals
List Originating Venues
list_originating_venues → 200401404422
GET
/list-supreme-court-decisions/FederalAppeals
List Supreme Court Decisions
list_supreme_court_decisions → 200401404422
GET
/list-remedies/FederalDistrict
List Remedies
list_remedies → 200401404422

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are FederalDistrictCourt (4 properties), JudgmentSourcesList (4 properties), FederalDistrictFindingsList (3 properties), StateCourt (3 properties). Each schema is shown below with its type and property counts.

CourtType
string
PossibleCaseResolution
object
2 properties 2 required
Court
object
2 properties 2 required
OriginatingVenuesList
object
2 properties 1 required
RemediesList
object
2 properties 1 required
StateDamagesList
object
2 properties 1 required
JudgmentSourcesList
object
4 properties 3 required
FederalDistrictDamagesList
object
2 properties 1 required
JudgmentEventsList
object
2 properties 1 required
FederalDistrictCourt
object
4 properties 4 required
StateCourt
object
3 properties 3 required
CaseTypesList
object
2 properties 2 required
EventsList
object
2 properties 2 required
CaseTagsList
object
2 properties 2 required
CaseResolutionsList
object
2 properties 2 required
FederalDistrictFindingsList
object
findingsByPracticeArea: a dictionary where the key is the name and the values are all the relevant types for supported findings. patentInvalidityReasons: only…
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lex-machina-list-api-openapi.yml Raw ↑

Other APIs Lex Machina publishes across the network.

Lex Machina Alerts API
Lex Machina Analytics API
Lex Machina Attorneys API
Lex Machina Authorization API
Lex Machina Bankruptcy Cases API
Lex Machina Case Query API
Lex Machina Dockets API
Lex Machina Entities API
Lex Machina Federal Appeals Cases API
Lex Machina Federal District Cases API
Lex Machina Find API
Lex Machina ITC Investigations API
Where this information came from

This is an independent, third-party profile of Lex Machina List API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.