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 Law Divisions API

Divisions represent the hierarchical documents that make up statutes, regulations, and constitutions. Each document has a 'path' which uniquely identifies the document and where it resides in the hierarchy of the law.

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

Tagged areas include Law Divisions. 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 7 operations across 7 paths, and defines 6 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.

7 operations 7 paths 6 schemas 7 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 Law Divisions 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 7

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

Law Divisions 7

Divisions represent the hierarchical documents that make up statutes, regulations, and constitutions. Each document has a 'path' which uniquely identifies the document and where i…

GET
/api/v1/jurisdictions/{jurisdiction_key}/laws/{law_key}/divisions
Get a specific Law's Root Divisions
getRootDivisions 2 params → 200400401404
GET
/api/v1/jurisdictions/{jurisdiction_key}/laws/{law_key}/divisions/{path}
Get Division by Jurisdiction and OpenLaws path
getDivsisionsByPath 3 params → 200400401404500
GET
/api/v1/jurisdictions/{jurisdiction_key}/laws/{law_key}/divisions/updates
(Enterprise Only) Get a list of Divisions that were created or updated after a date.
getDivisionsUpdatedAfter 5 params → 200401404
GET
/api/v1/jurisdictions/{jurisdiction_key}/laws/{law_key}/divisions/{starting_path}/updates
(Enterprise Only) Get a list of Divisions that were created or updated after a date within a subtree of Divisions.
getDivisionsByPathUpdatedAfter 6 params → 200401404
GET
/api/v1/jurisdictions/{jurisdiction_key}/laws/search
Keyword Search within a Jurisdiction
keywordSearchDivisionWithinJurisdiction 5 params → 200400401404500
GET
/api/v1/jurisdictions/{jurisdiction_key}/laws/{law_key}/search
Keyword Search within a Jurisdiction and a specific lawkey for that Jurisdiction
keywordSearchDivisionWithinLaw 5 params → 200400401404500
GET
/api/v1/jurisdictions/{jurisdiction_key}/laws/citations
Lookup by Jurisdiction and Bluebook legal citation for a statute, regulation, or constitution
lookupByBluebookCitation 2 params → 200400401404500

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Division (26 properties), DivisionUpdate (12 properties), Error (6 properties), DivisionDisplay (2 properties). Each schema is shown below with its type and property counts.

NullableDate
stringnull
Nullable ISO 8601 Date
Date
string
ISO Date with additional support for positive and negative Infinity values to represent ranges.
DivisionDisplay
object
Minimal subset of Division properties. Useful for building lists and drill downs of Division hierarchies.
2 properties 2 required
Error
object
RFC9457 Problem Details
6 properties 2 required
DivisionUpdate
object
(Law Firm and Enterprise plans only) Divisions are the primary building block in OpenLaws. Each Division represents a document at a snapshot in time. Divisions…
12 properties 6 required
Division
object
Divisions are the primary building block in OpenLaws. Each Division represents a document at a snapshot in time. Divisions can contain child Divisions (and thu…
26 properties 18 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openlaws-law-divisions-api-openapi.yml Raw ↑

Other APIs OpenLaws publishes across the network.

OpenLaws Courts API
OpenLaws Jurisdictions API
OpenLaws Laws API
OpenLaws Opinions API
Where this information came from

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