The Doxpop API Version 2 was deployed on January 18, 2014. We have been careful to design these enhancements in a way that is backwards compatible. We expect that your applications will not require any code changes to run on version 2 of the API.
The production API at https://api.doxpop.com/ switched to Version 2 on September 30, 2014. The older version will continue to be available for some period of time (yet to be determined) at https://api.doxpop.com/v1.
You can connect attorneys and their clients on a case with the new <relationship> element with two subelements. The <other_actor_uri> subelement contains a URI pointing to the actor on the other side of the relationship. The nature of the relationship is indicated by the <relationship_verb> subelement. The relationship verb is typically either "Represents" or "Represented by".
You can think about the parts of a relationship as the parts of a simple sentence grammar with a subject, verb, and object. The subject of the sentence is the <actor> in the context of the case. The object of the sentence is the <other_actor_uri>.
For example, in the context of a defendant on a case, a relationship looks like this:
<actor_case>
<relationships>
<relationship>
<other_actor_uri>/actor/18106A135-89</other_actor_uri>
<relationship_verb>Represented by</relationship_verb>
</relationship>
</relationships>
<case>
...
</case>
<assigned_case_role>DEFENDANT</assigned_case_role>
...
<actor>
...
<actor_uri>/actor/18106PD304FD041-1</actor_uri>
...
</actor>
</actor_case>
This translates to a sentence like this: The defendant with actor URI /actor/18106PD304FD041-1 is represented by /actor/18106A135-89.
The attorney on the other side of this relationship looks like this:
<actor_case>
<relationships>
<relationship>
<other_actor_uri>/actor/18106PD304FD041-1</other_actor_uri>
<relationship_verb>Represents</relationship_verb>
</relationship>
</relationships>
<case>
...
</case>
<assigned_case_role>Attorney</assigned_case_role>
...
<actor>
...
<actor_uri>/actor/18106A135-89</actor_uri>
...
</actor>
</actor_case>
This translates to a sentence like this: The attorney with actor URI /actor/18106A135-89 represents /actor/18106PD304FD041-1.
Charge resources show some new information.
One new element indicates the unusual situation where the court reduces a felony charge to a misdemeanor.
<charge_reduced_to_misdemeanor>
The next three elements will show standard codes across the state of Indiana.
<charge_state_offense_modifier_code>
<charge_state_offense_code>
<charge_state_degree_code>
Like the three state codes in charges, there is one new element in disposition resources that will show a standard set of values across the state of Indiana.
<criminal_disposition_state_disposition_code>
There is one new element in minute resources that shows the date and time when the minute record was entered into the CMS.
<minute_creation_date_time>
One new element on case resources indicates when a case has been "marked as expunged" from the public record. For more information about the "marked as expunged" designation for Indiana cases, see Indiana Code IC 35-38-9, particularly IC 35-38-9-7(b) and IC 35-38-9-10.
<case_is_marked_expunged>
The list of courts available in the Doxpop API can be found in the courts resources at /courts.xml or /courts.json. The response is now sorted alphabetically by <court_case_prefix>.
Drivers license numbers are sensitive information that can be used for identity theft. We are masking all of drivers license numbers except the last four digits. It is still possible to search the API with a full DLN using the drivers_license request parameter.