JavaScript API Tree

If you need more than events and methods offer, the API tree will be of use

API allows you to do many things, such as creating video, updating video (and its data) and removing the same and as such allows you to do things your way, while still communicating with our servers.

It is good to point out that if you are looking for a way to do it quickly and easily, checking out our Browser Interaction pages might be a better option, while API is definitely good for all those things that you need a bit of extra touch on.

API Segments

There are 2 main parts of the API connected to your media:

  1. Main media element or container. For example "Videos"
  • Video object will work directly with a video and will hold all of the details of the same
  1. Streams
  • Streams are part of the video object and as such you can have many streams available under the same video and action on a single stream would not affect the video as a whole, just that specific stream.

All of the calls are done with the use of your Ziggeo application. This way you can easily have multiple applications on the same page doing their own API calls.

It also means that you will need to have the application already created and available at the moment that you are making the call. The best place to see how, is to check out our header page.

In our example here the application will be declared as follows, however options in the application generally can only affect the auth request.

Ziggeo (on page) Application Initialization

<script>
  var ziggeo_app = new ZiggeoApi.V2.Application({
    token:"APPLICATION_TOKEN",
    webrtc_streaming_if_necessary: true,
    webrtc_on_mobile: true,
    auth: true
  });
</script>

URL Structure

Working with Videos API

Working with Video Streams API