Developers

Our encoding platform is exposed exclusively through our RESTful web service.

Anatomy of an Encoding Job

1. Request

   You perform an HTTP POST to the our API URL (see documentation). The BODY of that request will be a plain-text XML document. Our RESPONSE to your initial request will also contain an XML document in the BODY indicating information about your newly created job.
   
   NOTE: You do not include the actual video file in your request - you only specify where our encoding platform is to retrieve it.

2. Process

   We pull your video file from the source location you specified, process it, then push each and every output back to the destination location(s) you specified.

3. Callback

   Once complete, if you indicated a callback URL in your request, we will HTTP POST a response (either success or failure) to the URL you specified. It will contain a plain-text XML document in the BODY describing the job status in detail.

Documentation

The particulars of how to call our API vary by version - as we are constantly adding new features. Documentation for all version is available below.

Current

This version should be used for all new development & integration.

Version 300 (released: 2011-11-09)

• New API call - Get list of active jobs.
• New API call - Get details about a job.
• Added H.264 profile selection.
• Added quality setting for video.
• Added quality setting for audio.
• Added "total N" capture rate.

Legacy

These are shown here for reference only. If you are using one of these versions, you should upgrade to our current version - as these are in danger of no longer being supported or are already unsupported.

Version 200 (released: 2011-09-01)

• Added multiple destination locations.
• Added timeout to source locations.
• Added authentication type to HTTP source locations.
• Added max_size for video and capture outputs.

Version 100 (released: 2011-08-01)

• Initial.