In addition to downloading or streaming the rendered video, you can instruct the render server to upload the video directly to a third party, such as Facebook, Youtube, S3, Azure, FTP or any HTTP server that accepts a file upload.
In order to upload a rendered video to a destination, you must supply a Upload Task Defintion with your render request:
{
"extension": MP4, WebM, etc.,
"async": Boolean, Async setting,
"onsuccess": URL, called on successful render and upload,
"onerror": URL, called on error,
"destination": {
destination parameters
}
}
| Field | Type | Description |
|---|---|---|
| extension Required |
String | "mp4", "webm", "flv", "jpg", etc. |
| destination Required |
Object | A destination definition (see specific Uploader) |
| async (Optional) |
Boolean (true/false) | If true, the request will return immediately with a status of 201 ("Accepted") Rendering and uploading will be performed in the background. Please note that there is a request limit (Quota) for asynchronous operations of 5 concurrent requests per account. |
| onsuccess (Optional) |
URL | |
| onerror (Optional) |
URL |
For synchronous calls, the request will return information from the upload destination. For S3 uploads this will be the public URL of the uploaded object, for Youtube the Youtube video URL, and so on.
For asynchronous calls, the system will call your onsuccess and onerror callbacks with a query parameter ("msg") that will hold the information from the upload destination. For S3 uploads this will be the public URL of the uploaded object, for Youtube the Youtube video URL, and so on.
Terms of Use | © 2017, Impossible Software, or its affiliates.