{"id":392,"date":"2016-02-02T13:34:04","date_gmt":"2016-02-02T13:34:04","guid":{"rendered":"https:\/\/www.vdocipher.com\/blog\/?p=392"},"modified":"2025-11-11T07:20:39","modified_gmt":"2025-11-11T07:20:39","slug":"video-upload-using-api","status":"publish","type":"post","link":"https:\/\/www-uat.vdocipher.com\/blog\/2016\/02\/video-upload-using-api\/","title":{"rendered":"Video upload from website or server to VdoCipher API"},"content":{"rendered":"

[Update 24\/05\/2018]<\/strong> This blog has been updated for API Version v3. A previous version of this blog used API v2. If you are using API v2 you can contact us at support@vdocipher.com<\/a>. You can use VdoCipher API v3 to build a workflow around your video website as suggested in this blog<\/a>. The complete API v3 reference, with sample codes for different backend languages, can be accessed from the API Sample Docs<\/a>.<\/em><\/p>\n

We use Amazon AWS storage to\u00a0store original user videos securely in AWS\u00a0S3. With an intent to automate their online business, many of our customers wish to allow their users to upload videos directly from their website. To enable this, we have an API\u00a0call that returns an authenticated policy document which is\u00a0used video upload into a S3\u00a0bucket allotted to your account.<\/p>\n

Step 1 (Obtain authorized access):<\/h4>\n

Create\u00a0authorized video\u00a0upload\u00a0request with your API secret key.<\/p>\n

Request<\/strong>\r\nEndpoint: https:\/\/dev.vdocipher.com\/api\/videos?title=videotitile\r\nMethod: PUT\r\nHEADER:\u00a0Authorization: Apisecret a1b2c3e4e5d6<\/pre>\n
Response<\/strong>\r\nContent-Type: application\/json\r\n\"clientPayLoad\":{\r\n \"policy\":\r\n \"key\":\r\n \"x-amz-signature\": ,\r\n \"x-amz-algorithm\": ,\r\n \"x-amz-date\": ,\r\n \"x-amz-credential\": ,\r\n \"policy\":  ,\r\n \"upload_link_secure\": ,\r\n}\r\n\"video_id\":\r\n<\/pre>\n
The API call has\u00a0returned a set of parameters that must\u00a0go with the video upload call to the AWS S3 endpoint. We shall refer to this JSON object returned above as uploadData<\/em>.<\/p>\n
The policy document is valid only for the next 1 hour. It is recommended to make the video upload immediately after creating the authorized access. There is also a soft restriction on the number of upload calls every hour<\/strong>, so it is advised to create it only after the user has chosen to upload the video. It should not be made every time somebody loads their dashboard or mobile app.<\/p>\n
This call must be made from a secure environment<\/strong> such as your server. This should not be called from\u00a0a mobile device or the browser to protect your API key. The uploadData<\/em> should then be passed to user’s device (mobile or browser) to\u00a0do the file upload.<\/p>\n
Step 2 (Video upload via S3 API):<\/h4>\n
Upload the file to amazon s3 directly. This upload can be made using server code or using an HTML5 form<\/a>. You can use any third party upload library to make the upload script. The famous ones already have tutorials on setting it up with S3 upload. Check out our documentation for the upload API<\/a> to know more.<\/p>\n
application\u00a0Request<\/strong>\r\nEndpoint:\u00a0https:\/\/{bucket}.s3.amazonaws.com\/\r\nMethod: POST\r\nForm-Data:\r\n 'x-amz-credential': uploadData['x-amz-credential'],\r\n 'x-amz-algorithm': uploadData['x-amz-algorithm'],\r\n 'x-amz-date' : uploadData['x-amz-date'],\r\n 'x-amz-signature': uploadData['x-amz-signature'],\r\n 'key' : uploadData['key'],\r\n 'policy' : uploadData['policy'],\r\n 'success_action_status' : 201,\r\n 'success_action_redirect' : 'http:\/\/example.com'\r\n 'file': <file content><\/pre>\n