Need state trial court data via¬†API?¬† Reach out. ūü§Ě

¬†ūü™Ą Almost everything you can access on our state trial court site can be delivered via¬†API.¬† Did you know? We Now Provide State Trial Court Data via¬†API.

Our API is set up to require authentication (in the form of a token) and then makes calls on these endpoints:

  1. Alerts –Similar to alert settings in our UI, one can create and delete an alert.  This is a way for our API users to manage active alerts.
  2. Case – Used to look up specific info ‚ÄĒ including: Case Number, Attorneys, Documents, Events, Parties + Refresh ‚ÄĒ on a case.  This is similar to a case in our UI with case information, parties, documents, events, etc.   
  3. Documents – Specific to document-related downloading, requesting, and purchasing.  This is similar to downloading a single document from our document pages and requesting and purchasing documents from events.  
  4. Judges – This is similar to judge bio pages in our UI.  
  5. Rulings – This is similar to a ruling page in our UI.  
  6. Search – Supports all Boolean and query searching identical to our Smart Search functionality.  Filtering, sorting and state coverage is supported here for ‚ÄĒ Cases, Documents & Rulings.  
  7. Usage¬†–¬†Returns¬†API¬†usage stats¬†for the current billing cycle. ¬†
  8. Webhooks – Manages webhooks for notifications from refreshes & alerts.

Responses may return additional tokens for seeing specific case information, the next page of results, etc.  As well, we do not send emails to API users, but instead require webhooks for document purchase and alert notifications.

API subscriptions are completely independent of UI subscriptions.  This means that document requests, purchases, content views, and activity preformed in our UI will not be tracked on the usage endpoint in our API.  API subscriptions are billed on the first of the month.

To learn more, contact us or reach out to