Encoding API with Comprehensive Documentation and API Clients
Video API REST
Our REST API documentation is fully interactive. By clicking on the POST Create Input call, the sidebar opens with the properties of the call, as shown below. The full URL of the create input call is shown on the top as well as the HTTP Method (POST). Additionally, the call has three attributes, i.e., url, username and password, while username and password are optionally indicated by an unfilled bullet point. These attributes must be posted as a JSON object to the resource.
Request Schema Definition
The exact schema definition is described for every call in the Request Schema section.
Programming Language Examples
The response of each call is a JSON exactly specified through the Response Schema in each call.
An example of a specific JSON response is also shown in each call.
API Console Interface
The REST API offers a console interface where each call can be executed and evaluated. Three methods are available:
- Production: The call can be sent directly to the Bitmovin system. This requires your correct API Key. The Bitmovin API will then respond with a JSON as described in the call.
- Mock Server: This method allows you to test your call against a Mock Server that responds basically with an error if your request is structurally invalid or with a sample response if your request is valid.
- Debugging Proxy: The debugging proxy outputs additional debugging information which can be used to trace errors in the request.
Typically you should validate your request with the Mock Server first. If the Mock Server returns a valid sample response you can execute the call against the Production Server. Executing a call on the Production Server will trigger an operation in the Bitmovin system and can relate to costs in your account, e.g., starting an encoding. Be aware that this call will be executed on the production service.
If you want to test a call you can edit the response body directly in the API documentation as shown in the figure below. The example url has been exchanged against a valid path to the well known Sintel video (http://ftp.nluug.nl/pub/graphics/blender/demo/movies/Sintel.2010.720p.mkv).
You will also have to exchange the API Key in the request header field bitcodin-api-key with the API Key from your account. This is only necessary if you want to test your call against the Production Server. The Mock Server as well as the Debugging Proxy accept any key.
The call will be executed by clicking on Call Resource. You can select the System (Production, Mock, Debugging Proxy) through the dropdown beside the button. The response from the selected system will the be shown below.
Each API Client has a Getting Started documentation, which describes the installation, setup, usage and has examples. All implementations are available open source on Github.
Use the Bitmovin Video API to Encode MPEG-DASH & HLS Content
Encode your content using the Bitmovin video API with the same technology as Netflix and YouTube in a way that it plays everywhere with low startup delay and no buffering
Follow Bitmovin on Twitter: @bitmovin