Clerk E-Certify application is built with a number of external interfaces to connect with host CMS systems and vice versa. The system is built with interfaces to allow seam-less integration with Clerk web portal or Clerk applications. Whether the end user is an online user or Clerk’s themselves or external government agencies, you are able to use the API specifications to integrate your system with Clerk E-Certify. The interfaces are broadly classified into two categories namely outbound connector interfaces and inbound connector interfaces.
Outbound connector interface it utilized by Clerk E-Certify to interface with diverse court CMS/Official Records systems to retrieve and process case information, docket information, docket images, official record grantor/grantee information and official record images.
Inbound connector interface is utilized by external systems such as Clerk CMS applications to interface with Clerk E-Certify. Inbound interface allows external applications to send document information for eCertification, utilize Clerk E-Certify shopping cart to hold and process customer requests, and complete payment processing.You can download Clerk E-Certify integration specification document for detailed instructions on accessing Clerk E-Certify API.
Download API Interface specification
Click on the link below to download Clerk E-Certify integration guide. This document includes technical specifications on both outbound and inbound connector interfaces.
Shopping cart integration
Clerk E-Certify shopping cart is a repository for storing user selected documents prior to check out. Document information can be added to the shopping cart using multiple methods provided by the Clerk E-Certify API. Please note that shopping cart is a temporary storage for storing document meta data and does not store the documents themselves. Please refer to the interface specification document for more details.Shopping cart can be launched as a new browser window or as a pop-up within your web portal.
Document verification integration
Clerk E-Certify shopping cart is able to process external document requests. This method is utilized in scenarios where the end user is searching Court/Official Record documents on Clerk’s web site. The Clerk’s web application is responsible for the authentication and authorization of the end user prevmissions and granting access to Court cases/Official Records and view images.
Subscriber code and token must be obtained to interface with Clerk E-Certify. Your subscriber code and token is unique per subscriber and should not be shared with any one. Subscriber code and token is not included within this documentation. Please contract TRIEDATA to obtain your subscriber code and token.
Note: Your subscriber code and token may differ between the test and the production environment.
Online process integration with Clerk E-Certify is a two-step process. In step one, the Clerk’s web application sends the docket metadata information as an HTTP POST message to Clerk E-Certify web application with a unique identifier. Clerk E-Certify will save this information in its system. In the second step, Clerk’s web application redirects the user to Clerk E-Certify shopping cart passing in the unique identifier for completing payment processing.
After completing step one, there are two ways to launch the shopping cart.
Following data elements are transferred to Clerk E-Certify as part of the HTTP Post:
|Case number (UCN format)||Case number for court records and blank for Official Records|
|Case type (value = “UCN” p=or "LOCALCASENUMBER")||Case type such as "UCN" or "Local Case Number" or blank for Official Records|
|Docket description||Document description|
|Docket number (‘Document ID’ and ‘Document Version’)||Docket number or Official Record Instrument number|
|Page count||Number of pages within the document|
|Redaction Flag||Requesting redacted or unredacted image flag|
|Quantity||Requested quantity of document|
You may use native methods or ClerkeCertifyConnector DLL to send information to Clerkecertify. Please consult the interface specification guide to select the right option for your application.
After forwarding selected docket/instrument information using ClerkecertifyConnector API, you can redirect the user to view the shopping cart. User can confirm the details and complete the checkout process using a valid US issued credit card. This is one of the easiest ways to integrate shopping cart with your application.
instead of redirecting the user to clerkecertify.com for checkout, you may use Java script to launch the shopping cart as a modal pop-up window within your application. Clerkecertify shopping cart will be displayed as a popup window as shown above. This method offers tighter integration and will inherit the look and feel of your application.
Here are the steps for integrating shopping cart as a popup window
Clerk E-Certify offers two methods for verifying certified documents. The first method is to verify by unique code and the second method is to upload the certified document.
Verify by code method is used by either entering the unique code on Clerk eCertify web site or by scanning the QR code embedded on the first page of the certified document. The system confirms the validity of the code and optionally allows the user to download watermarked original document for side-by-side comparison. Verify by code user interface can be launched by two methods.
Verify by file upload method is used for validating electronic copy of the certified document. Users can upload the document and the system will perform an exhaustive set of checks to verify the authenticity of the document.
Verify by file upload is the most authentic and easiest way to validate a certified copy. This method validates a variety of security features within the document and does not require the user to view the original document. Since this method is able to analyze cryptographic signatures embedded within the document and able to indepependantly confirm authenticity of the document, this method is always preferred if the end user has access to the electronic copy of the certified document.
Further, all certified documents can be verified by this method and does not require a side-by-side comparison. Since certain court documents are not allowed to be displayed to general public, this method is the preferred method for validating all document types. There are two ways to validate an electronic file...