e-File API Reference

The MiCOURT eFile API is used to create, update and perform actions and events on a case. This API may only be called by developers with a Case Management subscription.

Case Initiation

A POST to the /cases resource is used to initiate a case. In this request, you can create a case, add participants to the case, and add initiating document events.

Per the request schema, the following data are required: the case number, the case type, the date the case was filed and the ID of the clerk who accepted the filing (as stored in the court's case management system). Depending on the case type and participant types, additional business rules may apply.

If successful, the response will contain the newly-created Case Docket ID in the request body and a Location header value indicating the URL of the case resource.

Validations are in place to ensure data quality. Different validations may apply depending on the type of case being initiated. For a full list of validations, see the Case Initiation Business Rules reference.

Case Actions

After a case is initiated (or working with an existing case) additional actions can be performed on the case.

Case Identifier

Once a case is initiated, you'll use the Case Docket ID to perform subsequent actions on the case. This uniquely identifies the case in the court. The case docket ID is defined as:

{case year}-{case number}-{case type}

For juvenile cases in our Probate Case Management System (PCS), there is an additional identifier:

{case year}-{case number}-{case type}-{suffix}

The Case Docket ID is included in the response when you initiate a case and can be found in the response when searching for a case as well.

Document Filing

A POST to the /documents resource is used to record a document filing event to the specified case.

Per the request schema, the following data are required: the type of document that was filed, the initials of the clerk who accepted the filing (as stored in the court's case management system), and the date the clerk accepted the filing. Optionally, you may associate the document filing event with a specific case participant, an attorney, or a judge. For juvenile cases within the Probate Case Management System (PCS), the filing event may be associated to one or more petitions.

If successful, a Location header will indicate the URL of the resource that can be used to pull all events for this case.

Validations are in place to ensure data quality. Different validations may apply depending on the type of filing and/or the type of case being filed to. For a full list of validations, see the Document Filing Business Rules reference.

Add a Participant

A POST to the /participants resource is used to add a new participant (party) to the specified case.

Per the request schema, the following data are required: the participant type, the date the participant was requested to be added to the case, the initials of the clerk who accepted the filing (as stored in the court's case management system), and the name of the person or organization denoted as a participant. The value of the isPerson flag determines which name - person or organization - is required.

Optionally, you may include a document filing event with this request. The same schema rules described in the Document Filing section above apply. The participant being added will automatically be associated with the document filing event.

If successful, a Location header will indicate the URL of the participant resource.

Validations are in place to ensure data quality. Different validations may apply depending on the type of case the add request is for. For a full list of validations, see the Add Participant Business Rules reference.