ScannerVision Web Server

JsonMetadataUploadRequest

**JsonMetadataUploadRequest** Parameters:
Name	Parameter	Data Type	Required
UploadFileName	query	string	No
OriginalFileName	query	string	No
TemplateGuid	query	string	No
ClientIpAddress	query	string	No
ClientGuid	query	string	No
ClientName	query	string	No
ClientId	query	string	No
ClientSerialNumber	query	string	No
UserName	query	string	No
UserEmail	query	string	No
UserHomeFolder	query	string	No
TemplateQuestions	query	IDictionary<string, string>	No
GlobalQuestions	query	IDictionary<string, string>	No

**JsonRequestDto** Parameters:
Name	Parameter	Data Type	Required
ClientCode	form	string	No
ClientRegistrationCode	form	string	No
Token	form	string	No

**JsonMetadataUploadResponse** Parameters:
Name	Parameter	Data Type	Required
TemplateGuid	form	string	No
InError	form	bool	No
ErrorMessage	form	string	No

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 /json/reply/JsonMetadataUploadRequest HTTP/1.1 
Host: buildmax.org 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"UploadFileName":"String","OriginalFileName":"String","TemplateGuid":"String","ClientIpAddress":"String","ClientGuid":"String","ClientName":"String","ClientId":"String","ClientSerialNumber":"String","UserName":"String","UserEmail":"String","UserHomeFolder":"String","ClientCode":"String","ClientRegistrationCode":"String","Token":"String"}

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

{"TemplateGuid":"String","InError":false,"ErrorMessage":"String"}