Secured Signing API

<back to all web services

AttachmentUploaderRequest

Attachment
The following routes are available for this service:
POST/Attachment/UploaderUploads a file by mulitpart formUploads a file using multipart form type. Allowed FileTypes: .pdf, .doc, .docx, .odt, .rtf .xls, .xlsx, .ods, .txt, .gif, .jpeg, .jpg, .png, .bmp, .dcm, .svg, .tif, .tiff.
AttachmentUploaderRequest Parameters:
NameParameterData TypeRequiredDescription
AnyThingmodelobjectYes
NumberquerystringNoAttachment Number, can only be digitals
CategoryquerystringNoAttachment Category
AttachmentResponse Parameters:
NameParameterData TypeRequiredDescription
ReferenceformstringYesAttachment reference
AttachmentFileInfo Parameters:
NameParameterData TypeRequiredDescription
NumberformstringNoAttachment Number, can only be digitals
CategoryformstringNoAttachment Category
FileInfoBase Parameters:
NameParameterData TypeRequiredDescription
NamemodelstringYesFile Name
FileTypemodelstringYesFile type of file

Allowable Values

  • pdf
  • doc
  • docx
  • rtf
FileUrlmodelstringYesUrl to download retrieve file data

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 /Attachment/Uploader HTTP/1.1 
Host: api.securedsigning.com 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"AnyThing":{},"Number":"String","Category":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"Reference":"String","Number":"String","Category":"String","Name":"String","FileType":"String","FileUrl":"String"}