Legal and case-law research
Usa los endpoints de CourtListener para convertir legal and case-law research en solicitudes API repetibles con inputs documentados y respuestas JSON.
Turn CourtListener's free legal database into structured JSON — full-text search across published court opinions with normalized result metadata, and a browsable directory of U.S. courts, all from CourtListener's anonymous public search.
Search CourtListener's public court-opinion index and browse its court directory as structured JSON, for legal and case-law research.
Familias de endpoints
3
Parámetros documentados
9
Ejemplos
3
Snapshot en vivo del catálogo
Endpoints activos
3
Métodos
GET
Parámetros obligatorios
4
Referencias de esquema
3
{
"platform": "CourtListener",
"endpoint": "courtlistener-courts",
"method": "GET",
"path": "/courtlistener/courts",
"auth": "apiKey"
}Casos de uso
Search CourtListener's public court-opinion index and browse its court directory as structured JSON, for legal and case-law research.
Usa los endpoints de CourtListener para convertir legal and case-law research en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de CourtListener para convertir court opinion monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de CourtListener para convertir litigation and compliance intelligence en solicitudes API repetibles con inputs documentados y respuestas JSON.
Ejecución gestionada
Cada cifra de abajo se lee directamente del catálogo de endpoints en vivo de CourtListener — 3 endpoints, 9 parámetros de solicitud documentados y 3 esquemas de respuesta publicados — el mismo catálogo contra el que corren Docs y Playground.
3 documented CourtListener endpoints, grouped into 3 request families — Courts, People and Search.
9 request parameters are documented across those CourtListener endpoints, 4 of them required — the full input contract is public before you write any integration code.
3 of the 3 CourtListener endpoints ship a recorded example response, and 3 carry a documented response schema — you can code against the real JSON before the first request.
CourtListener endpoints document their error responses (400, 404, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
3 hosted MCP tools back the CourtListener endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Mapa de cobertura
/courtlistener/courts
/courtlistener/people
/courtlistener/search
Catálogo de endpoints
/courtlistener/courtsLists CourtListener's anonymous public court directory. Provide court_id to retrieve one court. page is used only for directory browsing and is 1-indexed. The endpoint does not retrieve dockets, opinions, judges, or account data.
Herramienta MCP courtlistener_courts
/courtlistener/peopleLists CourtListener's anonymous public judicial-person directory. Provide person_id to retrieve one public person record. The response contains only public directory and position-summary metadata; sensitive biographical fields are excluded.
Herramienta MCP courtlistener_people
/courtlistener/searchSearches CourtListener's opinion-search index by text and returns opinion-result metadata with a cursor for the next page. The endpoint does not return opinion detail, dockets, judges, alerts, or account data.
Herramienta MCP courtlistener_search
APIs relacionadas
Business & Market Intelligence
Turn public GitHub ecosystem signals into structured data for developer-market research, open-source intelligence, recruiting, and AI-agent workflows.
Business & Market Intelligence
Collect public TrustMRR startup marketplace and leaderboard data as normalized JSON for startup research, SaaS discovery, and market intelligence workflows.
Business & Market Intelligence
Add website and competitive intelligence signals from SimilarWeb to research pipelines.
Cómo hacer scraping de CourtListener
CourtListener publishes court opinions and a court directory as anonymous public search data. Crawlora's CourtListener endpoints return normalized results as JSON with one API key — no scraper or search-index client to maintain.
Send a text query to /courtlistener/search for normalized opinion-result metadata, with a cursor to page through further results.
Call /courtlistener/courts to list CourtListener's public court directory, or pass court_id to retrieve one specific court's detail. page is 1-indexed and used only for directory browsing.
Preguntas frecuentes
Send a text query to Crawlora's /courtlistener/search endpoint and get normalized opinion-result metadata back as structured JSON, with a cursor to page through additional results — no need to build your own legal search index.
No — CourtListener endpoints use CourtListener's anonymous public opinion-search and court-directory data only. They do not retrieve authenticated opinion detail, dockets, judges, alerts, or account data.
Collecting publicly accessible opinion-search and court-directory data is generally permissible if you respect CourtListener's terms of use, robots directives, rate limits, and applicable law. This is for public data you are authorized to collect.