Secured Signing API

UserRequest

Account

The following routes are available for this service:
GET	/Account/Users	Get users in the account	Get users in the account.

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

HTTP + XML

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

GET /Account/Users HTTP/1.1 
Host: api.securedsigning.com 
Accept: application/xml

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

<ArrayOfAccountInfo xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/SecuredSigning.Api.Rest.Models">
  <AccountInfo>
    <AccountStatus>String</AccountStatus>
    <Actived>false</Actived>
    <DateFormat>String</DateFormat>
    <DefaultDueDate>0</DefaultDueDate>
    <DocumentLeft>0</DocumentLeft>
    <DocumentRemain>0</DocumentRemain>
    <DocumentUsed>0</DocumentUsed>
    <Email>String</Email>
    <EnabledDocNegotiation>false</EnabledDocNegotiation>
    <EnabledFaceToFaceSigning>false</EnabledFaceToFaceSigning>
    <EnabledReviewBeforeSigning>false</EnabledReviewBeforeSigning>
    <EnabledVideoConfirmation>false</EnabledVideoConfirmation>
    <GMT>String</GMT>
    <InDefaultPlan>false</InDefaultPlan>
    <IsAdmin>false</IsAdmin>
    <Locked>false</Locked>
    <MaxDueDate>0</MaxDueDate>
    <MaxUploadSize>0</MaxUploadSize>
    <Name>String</Name>
    <NotaryEnabled>false</NotaryEnabled>
    <PlanName>String</PlanName>
    <Upgrade>String</Upgrade>
    <UserId>String</UserId>
  </AccountInfo>
</ArrayOfAccountInfo>