Building Applications with the Windows Azure Media Services REST API
Updated: February 13, 2014
Windows Azure Media Services is an OData-based REST service that exposes objects such as Assets, Jobs, Tasks, and so on, as entities that can be queried in the same way as other OData entities. Furthermore, Media Services is built on OData v3, which means you can submit HTTP request bodies in atom+pub or verbose JSON, and receive your responses in the same formats.
This series of topics takes you through a high-level overview of using the Media Services REST APIs to achieve the end-to-end experience of ingesting content, processing it, managing it, and delivering it. Each section has a description of the process, example HTTP requests and responses, and links to reference documentation for more information about the entity or entities used in the process.
|All examples use JSON because it is lightweight and easily consumed by a variety of clients.|
Media Services Development Tasks using the REST API
Each topic in this list contains a set of Media Services developer tasks based on the Media Services application workflow. Each category is effectively a Media Services developer scenario.
Shows how to identify Media Services entities by their content identifier schemes.
Show how to carry out typical management operations with media assets and other entities on the server, including listing, updating, and deleting various Media Services objects.
Shows how to deliver media content from Media Services, either as a download, or as a URL to a file or to streaming content.