LexisNexis and Westlaw API Alternatives for Developers: How Access Works

If you are building software that needs US legal data, one question comes before any code: where does the data come from? An API (application programming interface) is a way for your software to ask another system for data. Different sources of legal data hand out API access in different ways, and the way they do it often decides what you can build and how fast.

Short answer: LexisNexis and Thomson Reuters (which owns Westlaw) both run developer programs, and neither lists a price on the pages we read. LexisNexis asks you to fill in a request form, and Thomson Reuters points you to its sales team for keys. vLex runs a developer portal where you sign up for an API account. For federal rules and bills, govinfo and Open States publish public APIs, and for statutes and regulations retrieved by citation there are commercial APIs such as Vaquill AI's. The right choice depends on whether you need a company's case law and editorial content, or the text of the law itself.

Reviewed and corrected on 12 October 2026. This is general information, not legal advice.

TL;DR

• LexisNexis: its Lexis APIs page says you request access through a form and, once approved, receive credentials and documentation. Pricing depends on the products and data volumes you need. Details are in our LexisNexis API guide.
• Thomson Reuters (Westlaw): its Developer Portal opened on April 10, 2024 with over 100 APIs across legal, risk and fraud, tax and trade. Its announcement says to connect with sales for a subscription. Details are in our Westlaw API guide.
• Other routes exist. vLex has a sign-up developer portal, govinfo and Open States publish government data, and a statutes API covers the code layer by citation.
• Case law and statutes are different layers of data. Many projects need one, some need both, and they can come from different places.

Part of our MCP and developer guide series.

For related MCP / API / developer coverage, see Best Legal Data APIs for Developers in 2026.

The options at a glance

"Access" below means how you get a working key, based on each source's own pages. A dash means the pages we read do not say.

The rows do different jobs. A research-platform API gives you that company's content. A government API gives you official documents. A statutes API gives you structured text of the code. Compare each one against your use case.

How access works at LexisNexis and Thomson Reuters

Both companies have real developer programs.

LexisNexis lists a Protégé API for its AI assistant, REST APIs to search legal and news content, and separate APIs for dockets (CourtLink), litigation analytics (Lex Machina) and legislative tracking (State Net). Its page says you apply through a form, and approved teams receive credentials for a developer portal with documentation and a test area called a sandbox. The portal's own Getting Started page says registration is free and gives access to documentation. LexisNexis says pricing depends on the products and data volumes you need.

Thomson Reuters launched its Developer Portal on April 10, 2024. Its press release describes over 100 APIs, and LawSites reported content from Checkpoint and Westlaw, including Westlaw U.S. Litigation Analytics. A Thomson Reuters community post from launch day says that to get keys you connect with sales for a subscription.

What does that mean for a developer? A request-and-approval model fits a team that already buys a research subscription and wants the same content inside its own tools. A sign-up key fits a prototype you want working this afternoon. Neither is better. They suit different projects, so ask early which one you are dealing with.

For questions about AI products specifically, our guide to whether Lexis+ AI and CoCounsel have an API covers what each company says.

Two kinds of data: case law, and statutes with regulations

Research platforms feel like single products, but a developer usually needs two different kinds of data from them:

1. Case law. Court opinions, dockets and citations. Examples are Carpenter v. United States, 585 U.S. 296 (2018), and Miranda v. Arizona, 384 U.S. 436 (1966).
2. Statutes and regulations. The U.S. Code (laws passed by Congress), the Code of Federal Regulations (rules written by federal agencies) and the 50 state codes. Examples are 42 U.S.C. 1983, 17 U.S.C. 107 and 5 U.S.C. 706.

These are different markets with different publishers and different prices. A project that only needs the second kind may not need a case-law subscription, and a project that needs both can buy each layer from the source that fits. If you want a framework for judging any legal API (request shape, latency, freshness, licensing), Legal API, explained walks through five axes.

A short history of how legal data reached developers

Developers did not invent the idea that legal data is licensed. It runs back to a few rulings and a few product launches.

In the 19th century the US Supreme Court decided who could own what. In Wheaton v. Peters (1834) it held that no reporter can hold a copyright in the Court's opinions. In Callaghan v. Myers (1888) it said a private reporter can own the headnotes, summaries and tables of contents he writes himself, because he does not speak with the force of law. The Court retold all this in its 2020 decision in Georgia v. Public.Resource.Org, which added that "no one can own the law." The opinion is on Cornell's Legal Information Institute. Put simply, the law's text is free to use, and the editing around it can be sold.

The online era began with Lexis, which LexisNexis's own history dates to 1973, and Westlaw, which a University of North Carolina library guide dates to 1975. The same guide says Westlaw.com reached ordinary web browsers in 1998. LexisNexis says it launched its first web-based service for US legal professionals in 1997.

Page numbers turned out to be data too. In 1986 the Eighth Circuit ruled in West Publishing v. Mead Data Central that West's arrangement of its case reports, including its page numbers, was protectable. The case was about adding West's page numbers ("star pagination") to LEXIS, so a reader could see where a passage sat in the printed book. On November 3, 1998 the Second Circuit went the other way on a different set of facts: it affirmed that inserting West's page numbers into a CD-ROM did not copy a protectable element (in a companion opinion), and that the small corrections West makes to opinion text showed too little creativity to protect. That dispute was about the parts a rival wanted to copy. It set aside West's syllabi, headnotes and key numbers. Two courts, two answers, and a reminder that the line between the law and the editing around it has been argued over for decades.

Programmatic access came late. LexisNexis launched its API developer portal on March 10, 2022, and Thomson Reuters launched its developer portal on April 10, 2024. Bob Ambrogi, who covers legal technology, noted in his LawNext report on the second launch that LexisNexis had launched a portal of its own in 2022. Since then AI tools have added another way in: Anthropic published its Model Context Protocol (a standard way for AI tools to connect to outside data) on November 25, 2024, and vendors now offer connectors built on it.

The takeaway for a buyer: expect each source to hand out access in the way its history set up. A publisher that has sold editorial work since the 1870s tends to sell access by contract. A government publisher tends to offer keys through a simple sign-up.

Government APIs: govinfo and Open States

A large share of US law is published by the government, with APIs.

govinfo, run by the U.S. Government Publishing Office, publishes the Federal Register, the Code of Federal Regulations, the U.S. Code and congressional bills. Its API uses an api.data.gov key, and the api.data.gov developer manual lists a default limit of 1,000 requests per hour per key, noting that limits can vary by service. The govinfo developer hub also describes a search service and a public preview of an MCP server (a connector that lets AI tools read the data).

Open States covers state legislatures. Its v3 API returns bills, legislators, committees and events for the states, DC and Puerto Rico. Its documentation says keys are required and does not publish request limits, so ask the project about volume.

These sources come as documents and metadata. govinfo is federal and Open States covers bills, so neither gives you the enacted code of all 50 states as one structured set. What you still have to build on top of this data is the next layer.

A statutes API for the code layer

Keeping US statutes current is real engineering work. Every state publishes its code in its own format, amends it on its own schedule and numbers its sections in its own way. Tracking amendments, handling renumbering and matching citations across states is steady maintenance.

Vaquill AI's API is built for US statutes, regulations, court rules, agency guidance and other primary law, retrieved by citation. Per its live OpenAPI document and coverage data as of 12 October 2026, it covers the U.S. Code and Statutes at Large, the CFR, the statutory codes of the 50 states, DC, Puerto Rico, Guam, the Northern Mariana Islands, the US Virgin Islands and American Samoa, state regulations, court rules, constitutions, federal agency guidance and adjudications, and the Federal Register. You can search, resolve a citation to its exact section, fetch the full text and read a section as it stood on a past date. The statutes API page lists the full surface, and the Federal Rules of Procedure guide shows one slice in detail.

The cost comparison for this layer is in Legal API vs building a RAG pipeline.

Why verifiable sources matter

Whatever you choose, an answer from your product should carry a citation a person can open and check, back to the official source the text came from.

The reason is on the court record. In Mata v. Avianca (2023), lawyers filed a brief that cited cases a chatbot had invented, and the court sanctioned them. Courts have since seen many more filings with fabricated citations. In 2024 the Supreme Court decided Loper Bright v. Raimondo, 603 U.S. 369, ending the old rule that courts defer to an agency's reading of an ambiguous statute, so courts now read the statute text themselves. ABA Formal Opinion 512 (July 2024) covers lawyers' duties when they use generative AI, including understanding the tool and checking its output.

You cannot verify what you cannot trace.

Who owns what now

Ownership changes affect contracts, so check them when you pick a supplier. Thomson Reuters closed its acquisition of Casetext, maker of CoCounsel, on August 17, 2023, for $650 million in cash. Clio announced on November 10, 2025 that it had completed its US$1 billion acquisition of vLex. Ask any supplier who your contracting party is, and what happens to your terms if the company is sold. Our ten questions to ask a legal data vendor include that one.

A decision path

Start with what you need, and follow the first line that fits.

1. You need a specific company's content, such as Westlaw or Lexis research content or Lex Machina analytics. Go to that company's request route and read its guide: LexisNexis or Westlaw.
2. You want a broad legal-document source with a sign-up portal. Look at the vLex developer portal, and check which APIs and terms apply to your plan.
3. You need the Federal Register, CFR, U.S. Code or bills as official documents. Start with govinfo.
4. You need state bills and legislators. Add Open States.
5. You need statutes, regulations and rules as structured text, found by citation. Use a statutes API, such as the one on our primary law API page.
6. For any source, keep your AI layer grounded in retrieved, citable text, and run the ten vendor questions before you sign.

The legal-tech developer use case shows what teams build on top of these layers. For the wider map of where US law is published, see US Law Data: The Complete Guide. Questions about the API: contact@vaquill.ai.

FAQ

What are the options besides the LexisNexis and Westlaw APIs?

vLex has a developer portal with an API sign-up. govinfo and Open States publish government data, and a statutes API covers the code layer by citation. Which fits depends on whether you need case law, official documents or structured statutes.

Is there a free Westlaw or LexisNexis API?

Neither company lists a free plan or a price on the pages we read. LexisNexis says pricing depends on products and data volumes, and Thomson Reuters says to connect with sales for a subscription. govinfo and Open States are public sources run outside those companies.

Does Westlaw have an API?

Thomson Reuters runs a Developer Portal with over 100 APIs, and reporting at its launch named Westlaw content among them. Our Westlaw API guide lays out who can use it and what it covers.

Does Lexis+ AI have an API?

LexisNexis lists a Protégé API that exposes "Ask" and "Summarize" features. Its price schedule notes that Lexis+ AI is now called Lexis+ with Protégé. See the Lexis+ AI and CoCounsel API guide.

What does the Vaquill AI API cover?

It covers US primary law retrieved by citation: the U.S. Code, the CFR, state and territory statutory codes (the 50 states, DC, Puerto Rico, Guam, the Northern Mariana Islands, the US Virgin Islands and American Samoa), state regulations, court rules, constitutions, agency guidance and adjudications, and the Federal Register. The API page has the details.

Can I get U.S. statutes and the CFR through an API?

Yes. govinfo publishes the U.S. Code and CFR as documents and metadata, and a statutes API returns them as structured, section-level text with matched citations. The US statutes API guide compares the main routes.

Should I use one vendor or several sources?

Both work. One vendor means one contract and one set of terms. Several sources let you pick the best fit for each layer, such as case law, official documents and statutes. List what you need first, then use the ten vendor questions to compare.

Priyansh Khodiyar

Co-Founder & CTO

Priyansh leads engineering and AI at Vaquill AI: the pipelines that pull statutes, regulations and court rules from every US jurisdiction's official publisher, and the REST API, MCP server and open dataset that serve them.