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

OpenLaws Opinions API

Opinions represent published and unpublished case law opinions. Opinions belong to a Court and Jurisdiction.

OpenLaws Opinions API is one of 5 APIs that OpenLaws publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Opinions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, a changelog, and rate-limit docs.

This API exposes 2 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.1.0, at version 1.0.4.

Requests are made against a single base URL, https://api.openlaws.us.

2 operations 2 paths 5 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.4
Base URL
https://api.openlaws.us
Authentication
HTTP Bearer
License
Resource Areas
1

Authentication & Security 1

OpenLaws Opinions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Authenticate API requests via a bearer token

Paths & Operations 2

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

Opinions 2

Opinions represent published and unpublished case law opinions. Opinions belong to a Court and Jurisdiction.

GET
/api/v1/jurisdictions/{jurisdiction_key}/opinions/search
Keyword Search Case Opinions
keywordSearchOpinions 8 params → 200400401404500
GET
/api/v1/jurisdictions/{jurisdiction_key}/opinions/citations
Lookup Case Opinion by Jurisdiction and Bluebook legal citation for a case
lookupOpinionByBluebookCitation 2 params → 200400401404500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Opinion (15 properties), Court (8 properties), Error (6 properties). Each schema is shown below with its type and property counts.

Opinion
object
Court opinions that resembles the CourtListener schema but is modeled to be focused on the Opinion as the central concept.
15 properties 3 required
DateTime
string
ISO 8601 DateTime
NullableDate
stringnull
Nullable ISO 8601 Date
Error
object
RFC9457 Problem Details
6 properties 2 required
Court
object
Represents a single Court and closely aligns to CourtListener's data set. Courts contain Opinions.
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openlaws-opinions-api-openapi.yml Raw ↑

Other APIs OpenLaws publishes across the network.

OpenLaws Courts API
OpenLaws Jurisdictions API
OpenLaws Law Divisions API
OpenLaws Laws API
Where this information came from

This is an independent, third-party profile of OpenLaws Opinions 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.