RHP_API

CreateEventVideo

Upload Event video

The following routes are available for this service:
POST	/User/Event/Video

**CreateUserVideoResponseItem** Parameters:
Name	Parameter	Data Type	Required
OriginalFileName	form	string	No
IsUploadSuccess	form	bool	No
Message	form	string	No
Video	form	UserVideo	No
ErrorCode	form	string	No

**UserVideo** Parameters:
Name	Parameter	Data Type	Required
Classification	form	PhotoClassification	No
VideoID	form	int	No
VideoUrl	form	string	No
ThumbUrl	form	string	No
Duration	form	int	No
ContentType	form	string	No
ContentLength	form	long	No
HSLVideoUrl	form	string	No
VideoCode	form	string	No

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 /User/Event/Video HTTP/1.1 
Host: tstsrvs.redhotpie.com.au 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<CreateEventVideo xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RHP_API.ServiceModel" />

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

<CreateUserVideoResponseItem xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/RHP.ServiceHelper.Model">
  <ErrorCode>String</ErrorCode>
  <IsUploadSuccess>false</IsUploadSuccess>
  <Message>String</Message>
  <OriginalFileName>String</OriginalFileName>
  <Video>
    <Classification>Undefined</Classification>
    <ContentLength>0</ContentLength>
    <ContentType>String</ContentType>
    <Duration>0</Duration>
    <HSLVideoUrl>String</HSLVideoUrl>
    <ThumbUrl>String</ThumbUrl>
    <VideoCode>String</VideoCode>
    <VideoID>0</VideoID>
    <VideoUrl>String</VideoUrl>
  </Video>
</CreateUserVideoResponseItem>