Notary Trust Registry SOAP and REST Web Service Interface

The Notary Trust Registry (NTR) SOAP and REST API allows you to query meta-data about specific e-notarized documents, and will allow you to add document meta-data into the registry.

Since the API is based on both SOAP and REST principles, it's very easy to write and test applications. You can use your browser to access URLs, and you can use pretty much any HTTP client in any programming language to interact with the API.

It is your responsibility to create and/or integrate the registry into your own applications or websites.  The API's provided have been designed for easy integration, and some programming may be required.

SOAP Endpoint and REST Base URL

All URLs referenced in the documentation have the following base:

https://api.notarytrustregistry.com

SOAP WSDL

https://api.notarytrustregistry.com/SOAP/NotaryRegister.svc?wsdl

The Registry's SOAP and REST API is served over HTTPS. To ensure data privacy, unencrypted HTTP is not supported.

Get e-Notarization Meta-Data

Get e-Notary Info

Add e-Notarization Meta-Data to the Registry

Add to Registry

Security Key

A Security Key is required in order to send and view registry data. Please email , with your name, company, email, and phone in order to request a Security Key.

About REST (REpresentational State Transfer)

We designed the Registry's API in a very RESTful way, so that your consumption of it is simple and straightforward. From Wikipedia:

REST's proponents argue that the Web's scalability and growth are a direct result of a few key design principles:

  • Application state and functionality are divided into resources
  • Every resource is uniquely addressable using a universal syntax for use in hypermedia links
  • All resources share a uniform interface for the transfer of state between client and resource, consisting of
    • A constrained set of well-defined operations
    • A constrained set of content types, optionally supporting code on demand
  • A protocol which is:
    • Client-server
    • Stateless
    • Cacheable
    • Layered

REST's client/server separation of concerns simplifies component implementation, reduces the complexity of connector semantics, improves the effectiveness of performance tuning, and increases the scalability of pure server components. Layered system constraints allow intermediaries-proxies, gateways, and firewalls-to be introduced at various points in the communication without changing the interfaces between components, thus allowing them to assist in communication translation or improve performance via large-scale, shared caching.

REST enables intermediate processing by constraining messages to be self-descriptive: interaction is stateless between requests, standard methods and media types are used to indicate semantics and exchange information, and responses explicitly indicate cacheability.

If you're looking for more information about RESTful web services, the O'Reilly RESTful Web Services book.

Windows .Net Web.config
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    <system.serviceModel>
        <bindings>
            <basicHttpBinding>
                <binding name="BasicHttpsBinding_INotaryRegister">
                    <security mode="Transport" />
                </binding>
            </basicHttpBinding>
        </bindings>
        <client>
            <endpoint address="https://api.notarytrustregistry.com/SOAP/NotaryRegister.svc"
                binding="basicHttpBinding" bindingConfiguration="BasicHttpsBinding_INotaryRegister"
                contract="NTR.INotaryRegister" name="BasicHttpsBinding_INotaryRegister" />
        </client>
    </system.serviceModel>
</configuration>