SecureVideo API

Support Center > API Integration

Published 12/31/2013 at 1:53am UTC

Page viewed 4103 times

Details

What is the SecureVideo API?

Answer

Videoconferencing API Overview

The SecureVideo API is useful for organizations looking to integrate videoconferencing with one or more organizational applications quickly and inexpensively. When combined with our branding feature, the API can allow you to have your users log onto your web application, schedule a session while on your web application, and then you can direct them to our system with your branded look, where they arrive already automatically logged in. Your users then see our dashboard with your company's colors, logo, and branded subdomain, but you don't have to do any more programming than that, as all notifications, presence, and connection code is already working. When your users log off (or their session times out), they are redirected back to the URL of your choosing (presumably on your web application).

Videoconferencing API Architecture

The API is RESTful and HTTP-based, using GET, POST, PUT, and DELETE HTTP methods to specific URIs, with each request returning a JSON object containing status and, where appropriate, a payload of data.

Pricing

Pricing will depend on a number of factors, including the nature of integration planned and the type and quantities of expected monthly transactions.  In general, customers can expect a set-up fee plus a monthly API access fee, which will be over and above videoconferencing monthly fees.  To get a quote, please contact us at (888) 200-7730 or info@securevideo.com.

Access

Once a customer has decided to go ahead with the API quote, we will execute an API Service Agreement.  Next, we will provide the customer with an API Access Key, which will enable the customer to start developing against and using the API.  Please note, there is only a production environment for the API.  Developers should create test user accounts as a way to develop and test their API implementations.

 

This article was last reviewed by our Support team on April 19, 2017.