Criminal Cases B1 Web Service Definition

Schedule 3

Referenced in Exhibit A of subscriber agreement

For notes on the Fair Credit Reporting Act (FCRA) and other general matters, see General notes on web services.

A SEARCHASES call is run first, based on name, with optional DLN or DOB.  The XML search results can then be used to decide identify cases of interest, which are then acquired using a GETCASE call.

Sample calls on Judici test server

If any of the following don't work, contact Web Service User Support

SEARCHCASES call

https://www.judici.com/service/caseSearchService?SEARCHCASES&USERID=n &APPID=a&KEY=0x &LITIGANTNAME=last, first [middle initial or name][&DOB=mm/dd/yyyy][&DLN=STn] [&OFFSET=n][FCRAFILTER=true|false] 

Authentication parameters

Service-specific required parameters

Optional parameters

Automatic filter criteria specific to this web service- ALL of the following conditions must be met for a case to appear

Query results pagination parameters- in the rare event that the person has a lot of cases, it may be necessary to obtain the results in multiple SEARCHCASES calls.  See Query results pagination attributes for more.

Data returned

GETCASE call

This call retrieves a litigant's case based on a CaseMD5 from a recent search and Litigant ID.

https://www.judici.com/service/caseSearchService?GETCASE& USERID=n&APPID=a &KEY=0x[&COURTID=ncic] &CASEMD5=value from SEARCHCASES result &LITIGANTID=value from SEARCHCASES result 

Authentication parameters

Service-specific required parameters

Data returned

As per T28 on Dec. 11, 2014

See sample GETCASE call above.   

All data describing a case in  CourtDataTransferFile are included, with the exceptions noted below.

The following elements have limitations:

The following elements aren't included at all: ActorRelationship, Offense, Receivable, Receivables, Payment, PaymentDistribution, BMVInfo, Event, Phone, Entry, RelatedActor, Document.  

For more on the data elements returned in response, see the CourtDataTransferFile documentation.