mncourts.gov and other court applications will be under maintenance from 6:00 p.m. on Saturday, June 15, 2024, through 1:00 p.m. on Sunday, June 16, 2024. You may experience intermittent outages during this time. If you are unable to access a website or service, please wait one hour and try again.

COURT INTEGRATION SERVICES

Court Integration Services enables authorized agencies’ systems to exchange information with the Minnesota Judicial Branch systems.

Notification Services allows an authorized agency's system to get court information as events occur from the Minnesota Judicial Branch. 

Bond Notification Service

The Bond Notification service is a mechanism that allows court business partners to have bond data delivered to their applications when specific events relating to Bonds occur in the Minnesota court case management system, MNCIS.  The information that is returned by the service is governed by the access rights the consumer has to MNCIS case records on their subscription.

BondAdded - A bond is added to MNCIS.
BondDeleted - A bond is deleted to correct a clerical error.
BondLinkedToCase - A free standing bond is linked to a case.
BondModified - Bond data is modified within MNCIS.
Bond Notification_3_5.xsd uses CourtXML version 3.3 Base schema
Bond Notification_3_5_NoEnum.xsd uses CourtXML version 3.3 Base schema without enumerations
CourtXML_3_3.xsd Base schema
CourtXML_3_3_NoEnum.xsd Base schema
For prior Schema versions, please view our CourtXML page.
Simple Type Schemas and Companion Files are required for CourtXML Base schema
MQ Series
       Defined by subscriber
 
Web Services     
Service Address: WebServices/ServiceCatalog/BondNotificationService_3_5.svc
A copy of the WSDL is available on our public website. By default this points at the Test/Quality Assurance (QA) environment. At runtime you will need to update the endpoint address to reflect the environment you are using.
Message Receiver Web Service developed using VB.Net with Visual Studio 2010.
Windows Application used to Pull Bond Notification messages developed using VB.Net with Visual Studio 2010.
Revised:06/14/2017