POST | /User/Event/Video |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
OriginalFileName | form | string | No | |
IsUploadSuccess | form | bool | No | |
Message | form | string | No | |
Video | form | UserVideo | No | |
ErrorCode | form | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
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 .jsv suffix or ?format=jsv
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: text/jsv
Content-Type: text/jsv
Content-Length: length
{
}
HTTP/1.1 200 OK Content-Type: text/jsv Content-Length: length { OriginalFileName: String, IsUploadSuccess: False, Message: String, Video: { Classification: Undefined, VideoID: 0, VideoUrl: String, ThumbUrl: String, Duration: 0, ContentType: String, ContentLength: 0, HSLVideoUrl: String, VideoCode: String }, ErrorCode: String }