Secured Signing API

<back to all web services

Uploader2Request

The following routes are available for this service:
POST/Document/Uploader/{ClientReference}Uploads a file with client reference by mulitpart formUploads a file using multipart form type. Allowed FileTypes: .gif,.jpeg,.jpg,.png,.bmp,.dcm,.svg,.tif,.tiff,.doc,.docx,.odt,.ods,.xls,.xlsx,.pdf,.rtf,.txt.
Uploader2Request Parameters:
NameParameterData TypeRequiredDescription
ClientReferencepathstringNoClient reference
AnyThingmodelobjectYes
FoldermodelstringNoUpload the file and put in a folder; Only 'InBox' supported; if put in inbox, the document will be charged and visible in web portal; by default, the document is in an invisible temporary folder and can only be used via API.

Allowable Values

  • InBox
MatterNumbermodelstringNoMatter/Ref Number
DocumentReferenceResponse Parameters:
NameParameterData TypeRequiredDescription
ReferenceformstringYesDocument reference, used for document access

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.

POST /Document/Uploader/{ClientReference} HTTP/1.1 
Host: api.securedsigning.com 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<Uploader2Request xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/SecuredSigning.Api.Rest.Requests">
  <AnyThing />
  <ClientReference>String</ClientReference>
  <Folder>String</Folder>
  <MatterNumber>String</MatterNumber>
</Uploader2Request>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<DocumentReferenceResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/SecuredSigning.Api.Rest.Models">
  <Reference>String</Reference>
</DocumentReferenceResponse>