LexisNexis API: What the Developer Portal Offers and How Access Works

Short answer: yes, LexisNexis has APIs, and it has a developer portal. An API (application programming interface) is a way for one piece of software to ask another for data. LexisNexis runs several of them, covering legal research content, court dockets, litigation statistics, news, company data and an AI assistant. You apply through a form, and if approved you receive credentials and access to documentation and a test area. LexisNexis does not publish a price for any of it.

TL;DR

• LexisNexis is several businesses. Legal, news and company data, and risk and identity products come from different units.
• Access is by request. The Lexis APIs page says you fill in a form and, once approved, receive credentials for the developer portal.
• The price is not published. The page says pricing depends on the products and data volumes you need.
• Terms on AI use are strict. The general terms (effective June 5, 2026) limit model training and outside AI tools.
• The "LexisNexis API" in library guides is a different product. It is mostly a news text-mining service run through university libraries.

LexisNexis is several businesses

People who search "LexisNexis API" want very different things: case law and statutes, news archives for research, or a check on a customer's identity. LexisNexis sells all of these, through different units. The legal side runs the Lexis research products and the Lexis APIs page. The Nexis side sells news, company and legal data feeds, and its Data+ support page links to a developer portal at dev.lexisnexis.com. A separate unit, LexisNexis Risk Solutions, sells fraud, identity and credit-risk products, and its own website lists them under those headings.

Pick the unit first.

A short history of Lexis

The "several businesses" point makes more sense once you see how the company was assembled. LexisNexis's own history page starts with the publishers it later absorbed: Butterworths in London in 1818, Matthew Bender in Albany in 1866, Martindale-Hubbell in 1868 and Shepard's in Chicago in 1873. Shepard's is known for its citator, a service that tells a lawyer whether a case has since been followed or overruled.

The online part began in Ohio. In 1967 the Ohio State Bar Association hired Data Corp, an Ohio company, to build a "free-text" search system, meaning you could search for any word in a document instead of looking up a heading. The Mead Corporation bought Data Corp a year later and in 1970 spun out Mead Data Central. On the history page's account, in 1973 Mead Data Central introduced LEXIS with the full text of Ohio and New York codes and cases, the US Code and some federal case law. So the first thing sold online was a mix of case law and statutes. The company says NEXIS, the news database, followed in 1979.

More pieces arrived through purchases. LexisNexis bought The Michie Company, a publisher of state codes founded in 1897, in 1988. Reed Elsevier acquired the business in 1994. In 1997 it launched its first web-based service for US legal professionals. In 2000 it started a unit for identity and risk products, and a year later it bought CourtLink, the court filings service. That is why the portal today spans legal research, dockets, news and risk: each line has its own origin and its own history.

Which APIs exist

The Lexis APIs page lists the following. The middle column follows LexisNexis's own descriptions, shortened.

The page also names a State Net content API and an MLex API that are not yet released, and it describes public-records data about people, businesses and property.

A 2022 LexisNexis press release also names URL APIs (simple links into the products) and bulk APIs (large data transfers). On the Nexis side, the dev.lexisnexis.com home page, read on October 5, 2026, leads with a data service called Nexis DaaS ("data as a service"). It lists bulk delivery, search and retrieve APIs, custom data feeds and a data lake. The data sets it names include news, company and financial data, sanctions lists, U.S. case law and legislation, and U.S. dockets.

How access works

The Lexis APIs page answers this in one paragraph. You request access through a form on that page. Once approved, your team receives credentials and onboarding details for the developer portal, "where you can explore documentation and test endpoints in a sandbox environment." A sandbox is a practice area where you can try calls without touching live customer data.

Two details help set expectations.

First, in March 2022 LexisNexis described the new portal as "self-serve" in its launch press release. The current page describes an approval step. Plan for a request, a review and a conversation.

Second, the Lexis APIs page does not give the portal's web address. The address LexisNexis links to as its Developer Portal is dev.lexisnexis.com, and that home page loads its content with scripts, so a plain page request returns an empty shell. A rendered copy shows the Nexis DaaS description above. In the text we read, there was no public list of endpoints, no reference documentation and no sign-up. LexisNexis's pages do not say whether the legal APIs and the Nexis data APIs share one portal, so ask which one you are being given.

In their words

When LexisNexis launched its API developer portal on March 10, 2022, its press release explained the idea through Jeff Pfeifer, then chief product officer for North America and the UK: "Our new API Developer Portal enables organizations to enrich and normalize their internal data by directly incorporating our industry-leading data and content."

The release is a useful read for a buyer because it spells out the access styles. It lists URL APIs, which are one-way links into the products, REST or web services, which need your own engineers, and bulk APIs for moving large data sets. It also describes four jobs the APIs are meant to do: bring content into your own work environment, combine it with your own data, alert you when something changes, and clean and tag your internal data. Match your project to one of those four before you ask for access.

What is documented in public

Without an account, as read on October 5, 2026, you can see the product descriptions on the Lexis APIs page. They include security claims: OAuth 2.0 (a standard sign-in method) for the Protégé API, plus SOC 2 and ISO security certifications. The 2022 launch announcement adds that the portal has a sandbox, data schema information and technical documentation. LexisNexis also publishes general terms and a price schedule, covered below.

The public pages show no endpoint lists, request examples, rate limits, uptime commitments or price. LexisNexis says the documentation sits inside the portal after approval. Ask to see it before you sign.

SDKs and code libraries

An SDK (software development kit) is a ready-made code package that makes an API easier to call. The Lexis APIs page says the portal offers "documentation, SDKs, sample code, and sandbox testing tools." The 2022 coverage in LawSites reported code samples in Shell, JavaScript, Python and Ruby.

Outside the portal, two public packages exist. A Python package named lexisnexisapi on PyPI (the public Python package index) is open source (MIT licence) and lists a LexisNexis author. Its documentation covers the Metabase API, one of the products on the Nexis Data+ page, and it needs a Metabase key. The Lex Machina team also publishes a Python client on GitHub under the open-source Apache 2.0 licence. It calls the Lex Machina API at api.lexmachina.com with an access token. Both need credentials before they do anything.

What LexisNexis publishes about price

This is the question behind searches for "lexisnexis api pricing." Here is the exact position.

• The Lexis APIs page says: "API access and pricing depend on the specific products and data volumes your organization needs." It points you to the request form.
• In 2022, a LexisNexis product executive told LawSites that API pricing would depend on a firm's package. For some customers APIs would be included, and for others they would be bought separately.
• LexisNexis does publish a price schedule for its research service. We read the small-law version, effective October 2, 2026. It lists per-document, per-report and per-alert charges for use outside a flat subscription. It never mentions APIs, so it is not an API price list.

No API price, tier or free plan appears on any page we read. Any figure you are given will come from LexisNexis directly.

Rules for using the content with AI

If you plan to feed legal text to a language model, read the terms first. LexisNexis publishes General Terms and Conditions, effective June 5, 2026. They cover its online services, and they apply to any agreement that includes them. In summary:

• You may not use the materials to train large language models or other AI.
• You may not upload materials to third-party AI tools, with one exception: a "Compliant AI Tool," meaning one with zero data retention and a ban on training with your content. Even then the use must be incidental, never bulk.
• You may not use an autonomous AI agent to access or query the online services, including through API calls, without written permission from LexisNexis.

These terms are written for the online services. Whether the same wording sits in your API order form is a question for LexisNexis, and the answer decides whether you can build an AI feature on the content. Get it in writing. LexisNexis also states on its API page that it never uses customer data to train AI models, which is a separate point about your inputs.

Why library guides rank for this search

Search for "LexisNexis API" and you will see pages from Stanford, Penn, Penn State and other libraries. They describe the LexisNexis Web Services API, a subscription service that lets researchers text-mine news and some other Nexis Uni collections. The Stanford guide says it needs basic to intermediate Python or R skills, and that Stanford has two seats and often a waiting list.

Access runs through the library. Penn State's guide says the service is temporarily unavailable, and NYU's guide says its subscription ended on March 31, 2025. This is a different service from the Lexis APIs for businesses, so you can skip those pages unless you are a university researcher.

What to check before you choose

1. Which business unit sells what you need? Legal research content, litigation analytics, dockets, news and identity checks are separate products.
2. Do you need the text of the law, or a finished answer? The Protégé API returns AI answers with citations. The REST APIs search and retrieve content.
3. Can you see the documentation before you pay? Ask for portal access during evaluation.
4. What does the contract say about AI? Training, outside AI tools and agents are all addressed in the general terms. Ask for the API terms.
5. What are the limits? Ask for rate limits, daily caps and what happens when you go over.
6. Can you show the content to your own customers? Display and resale rights are a separate question from access.
7. What happens at renewal or exit? Ask about notice and how long old endpoints keep working.

Our ten questions for a legal data vendor turn this into a checklist you can send to any supplier, LexisNexis included.

A fair decision path

• You need LexisNexis's own content, such as its dockets or litigation analytics. Go to the request form. Those products and their data come from LexisNexis.
• You want to put an AI assistant on LexisNexis content inside your own tools. Look at the Protégé API, and read our guide to whether Lexis+ AI and CoCounsel have an API.
• You are a university researcher mining news. Ask your library about the Web Services API.
• You need identity, fraud or credit checks. That is the Risk Solutions side.
• You need the text of statutes, regulations, court rules and agency guidance in your product. Government publishers offer free feeds for parts of it, and our comparison of statute and code APIs and guide to legal data APIs for developers cover the options. The complete guide to US law data shows where each kind of law is published.

The Westlaw API guide does the same job for Thomson Reuters.

Try it

For that last case, here is a short call to the Vaquill AI API, which is built for US statutes, regulations, court rules, agency guidance and other primary law, retrieved by citation. This asks for one federal statute by its citation:

curl -G "https://api.vaquill.ai/api/v1/us/statutes/resolve" \
  --data-urlencode "cite=42 U.S.C. 1983" \
  -H "Authorization: Bearer vq_key_YOUR_KEY"

If the citation matches a section, the response says resolved: true and returns the section's details. If it matches nothing, resolved is false. Keys come from the developer dashboard, and the US primary law API page has the details.

FAQ

Does LexisNexis have an API? Yes. The Lexis APIs page lists a Protégé API, REST APIs, CourtLink, Lex Machina, State Net, Law360 and Cognitive APIs. Access is by request and approval.

Is there a Lexis+ API? LexisNexis's 2022 portal launch listed Lexis+ among the products that have APIs. Today the company's API page describes REST APIs for searching and retrieving legal and news content, and a Protégé API for its AI assistant. Its price schedule notes that Lexis+ AI is now called Lexis+ with Protégé.

Is the LexisNexis API free? LexisNexis does not publish a free plan or a price. The API page says pricing depends on the products and data volumes. You have to ask.

Where is the LexisNexis developer portal? The Nexis Data+ page links to dev.lexisnexis.com as the Developer Portal. The Lexis APIs page says approved teams receive credentials for a developer portal with documentation and a sandbox, but it does not print the address, so confirm which portal you are given.

Can I use LexisNexis content with ChatGPT or another AI tool? The published general terms allow it only in narrow cases: a tool with zero data retention and a ban on training, incidental use, and no bulk extraction. Training models on the content is not allowed. Ask LexisNexis about your specific agreement.

Is "lexus nexus api" the same thing? Yes. People often misspell the name as "Lexus Nexus". The company is LexisNexis, and this guide covers the same APIs.

Can I get US statutes by API without a sales process? Yes, several sources work that way. Government publishers offer free feeds for parts of the law, and commercial APIs issue keys from a dashboard. The govinfo comparison shows what the free feed gives you and what it leaves out.

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.