We recently made a change to the schema for both Class Action cases and involving Patent Invalidity. Previously, in Class Action cases, the API for a given case returned only the general class action finding, such as “Class Certification: Deny,” and not the specific findings associated with the overall decision of whether to deny or grant class certification. Consequently, the schema was modified so that Class Action cases now return the following specific findings if relevant:
As part of our efforts to continuously improve and expand the capabilities of the Lex Machina API, we now have Appeals data available via the API.
The in-app documentation has been updated to reflect the changes, new endpoints and the new inputs to some of the list endpoints. Any of the endpoints that previously took “FederalDistrict” or “State” as input now also take “FederalAppeals” as context for the list of resources requested.
In the world of litigation, data-driven insights have become invaluable tools for legal professionals seeking to gain a competitive edge. As the creator of litigation analytics, Lex Machina has fundamentally altered the way legal research is conducted, providing comprehensive data and sophisticated tools to allow users to make informed decisions. Today we are thrilled to announce the launch of our API Sandbox! This allows potential API customers to experience the capabilities of our API firsthand before committing to a subscription.
The most recent state courts to be added to the Lex Machina data include nine county circuits from Oregon. These nine counties are from the top 11 most populous counties in the state so while 25% of the counties in Oregon, it covers 73% of the population. The goal is to expand to the rest of the counties by the end of the year. (This is an aspiration, not a promise or binding contract.
After long alpha and beta periods, much development and customer input the day has arrived. The Lex Machina API is in General Availability release!
This release now includes state court data. In order to create endpoints and schemas that have some consistency across district and state data, refactoring was necessary. For those who are directly implementing access to our API, this will require some changes to code. There is a guide to the changes in the developer portal at https://developer.
