Express Portal

   Home   |   Partners   |  Citation Code Standardization   |   LEA » Court   |   Court » State   |   Reporting   |   More Info

How to Query the AOC Citation Report Data WS



This document is intended for a user who is tasked with querying the AOC Citation Report Data Web Service. The examples will use raw XML since this is the lowest common denominator for clients and reporting tools.

About the Web Service

The AOC Citation Report Data Web Service was designed to give government entities access to disposed citation data through a secure and flexible channel for reporting purposes.

Obtaining Access

To access the service one will first need a user ID and password. The user ID and password will be sent with every query to the web service. A user ID and password can be obtained by contacting This email address is being protected from spambots. You need JavaScript enabled to view it.

How to make queries

The best way to understand how to make your own queries is to understand an example query and how the web service processes it. This section walks through an example using the DATERANGE procedure.

A client (reporting tool) will make a data request to the web service by providing a userID, password, procedureName, some parameters, and the needed fields.

Here is an example request:

<soap:Envelope xmlns:soap=""
               xmlns:ns2="" >
            <ns2:RequestHeader >

I'll break down how this request is handled by the web service. First the UserID and Password is evaluated. The Web service tries to locate a user with these credentials and if it finds one processing continues if not an “Invalid user and/or password” error is passed back.

Next the fields are verified by making sure that they are listed in the list of available fields. One can view this at The first field can contain the value "ALL" or "ALL_EXCEPT". "ALL" will return all fields. "ALL_EXCEPT" will create a list of all fields and then remove the remaining provided fields from the list. If any of the fields do not meet these criteria an error will be passed back explaining which fields were problematic.

 Use of “ALL” and “ALL_EXCEPT” should only be needed in very rare circumstances. Please explicitly request the fields that your application needs. This will minimize bandwidth and server load.

 Next the procedureName is validated. The procedure must come from the list of available procedures. This is viewable by visiting this link If the procedure is not in the list an error is returned.

Next the web service makes sure that the given number of parameters is equal to the number of parameter descriptions in the procedure. If you look at date range in the available procedures list you will notice it has 2 parameter descriptions:

  1. Starting Date Inclusive in MM/DD/YYYY format
  2. Ending Date Inclusive in MM/DD/YYYY format

 In this case 2 parameters must be given or an error will be sent back.

Next the parameters are validated for format. For the date range procedure the first and second parameter must be in MM/DD/YYYY format or an error will be sent back.

Now that validation has completed the web service will make a query to the database based on the citation request and the results will be returned. Here is an example response:

<soap:Envelope xmlns:soap="">

You can see that 3 records were returned that are in the date range 03/01/2010 - 05/31/2010 with the two specified fields EXPRESS_CITATION_ID and CITATION_DATE.