vzaar's uploading API allows 3rd party users to upload content directly into their account on vzaar.
This is done by 3rd parties performing an authenticated HTTP POST directly onto vzaar’s storage space. vzaar uses the Amazon S3 as it’s storage solution, and has exposed this via the vzaar API. Further links are at the end of this article to help understand how the Amazon S3 HTTP POST architecture works.
Uploading to vzaar is a 3 step process
- Sign: API call to vzaar to request signature and location details
- Upload: Upload to vzaar’s S3 space using the signature and location details
- Process: API call to vzaar to process uploaded file.
Guids vs vzaar Video ids
3rd party developers (or whitelabel) users will want to track files between the steps. In a typical scenario, the whitelabel account holder will have many users on their platform, and funnel their users videos through the one account on vzaar. The whitelabel user will want to associate which user of theirs uploaded which video.
- The return code for the Sign step, will contain a GUID.
- The return code for the Process step will contain a vzaar video ID.
The vzaar video id is the identifier that will be used to obtain the Video Details and perform operations on the video. This is the final identifier that must be recorded in the whitelabel users local database against their user who uploaded the video.
It’s recommended that the GUID is used to track the file until the vzaar video ID is returned from the process command. This should then be swapped in the local database for the GUID.