Secured Signing API

NotaryCheckRequest

Account

The following routes are available for this service:
POST	/Account/NotaryCheck	Check if user has notary setup in the account	Check if user has notary setup in the account.

**NotaryCheckRequest** Parameters:
Name	Parameter	Data Type	Required	Description
FirstName	model	string	Yes	First Name
MiddleName	model	string	No	Middle Name
LastName	model	string	Yes	Last Name
Email	model	string	Yes	Email

**NotaryCheck** Parameters:
Name	Parameter	Data Type	Required	Description
RonEnabled	form	bool	No
IpenEnabled	form	bool	No
OnlineActEnabled	form	bool	No
OnlineAct	form	string	No
NotaryEnabled	form	boolean	No	If the user is notary or not
CommissionId	form	string	No	Notary Commission ID
CommissionExpiry	form	string	No	Notary Commission Expiry Date
County	form	string	No	Notary Commission County
State	form	string	No	Notary Commission State
CertificateEnabled	form	boolean	No	If certificate setup or not
CertificateExpiry	form	string	No	Certificate Expiry Date

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /Account/NotaryCheck HTTP/1.1 
Host: api.securedsigning.com 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"FirstName":"String","MiddleName":"String","LastName":"String","Email":"String"}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"RonEnabled":false,"IpenEnabled":false,"OnlineActEnabled":false,"OnlineAct":"String","NotaryEnabled":false,"CommissionId":"String","CommissionExpiry":"String","County":"String","State":"String","CertificateEnabled":false,"CertificateExpiry":"String"}