Portal

BrowseSupplierFile

The following routes are available for this service:
GET	/supplier/{supplierid}/file/{supplierfileid}

**BrowseSupplierFile** Parameters:
Name	Parameter	Data Type	Required	Description
SupplierId	path	int	No
SupplierFileId	path	int	No

**BrowseSupplierFileResponse** Parameters:
Name	Parameter	Data Type	Required	Description
SupplierFile	form	SupplierFileDetails	Yes

**ResponseBase** Parameters:
Name	Parameter	Data Type	Required	Description
ResponseStatus	form	ResponseStatus	Yes

**SupplierFileDetails** Parameters:
Name	Parameter	Data Type	Required	Description
SupplierId	form	int	No
DocumentType	form	SupplierDocumentType	No

**BrowseFileResponseBase** Parameters:
Name	Parameter	Data Type	Required
Id	form	int	No
FileContentId	form	int	No
FileName	form	string	Yes
Size	form	long	No

**SupplierDocumentType** Enum:
Name	Value
RegistrationForm	0
SpecimenSignature	1

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.

GET /supplier/{supplierid}/file/{supplierfileid} HTTP/1.1 
Host: szallitoiportal-be.veolia.hu 
Accept: application/json

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

{"SupplierFile":{"SupplierId":0,"DocumentType":0,"Id":0,"FileContentId":0,"FileName":"String","Size":0},"ResponseStatus":{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}}}