Mock sample for your project: Wowza Streaming Cloud REST API Reference Documentation

Integrate with "Wowza Streaming Cloud REST API Reference Documentation" from wowza.com in no time with Mockoon's ready to use mock sample

Wowza Streaming Cloud REST API Reference Documentation

wowza.com

Version: 1

Use this API in your project

Open in the application
Download mock API file
📖 How to use?
Own this API? Add a Mockoon button on your website.

Speed up your application development by using "Wowza Streaming Cloud REST API Reference Documentation" ready-to-use mock sample. Mocking this API will help you accelerate your development lifecycles and allow you to stop relying on an external API to get the job done. No more API keys to provision, accesses to configure or unplanned downtime, just work.
Enhance your development infrastructure by mocking third party APIs during integrating testing.

Description

About the REST API
The Wowza Streaming Cloud TM REST API (application programming interface) offers complete programmatic control over live streams, transcoders, stream sources, and stream targets. Anything you can do in the Wowza Streaming Cloud UI can also be achieved by making HTTP-based requests to cloud-based servers through the REST API.
The Wowza Streaming Cloud REST API features cross-origin resource sharing, or CORS.
CORS is a W3C specification that provides headers in HTTP requests to enable a web server to safely make a network request to another domain.
In order to protect shared resources, the Wowza Streaming Cloud REST API is subject to limits. For details, see Wowza Streaming Cloud REST API limits.
About this documentation
This reference documentation is based on the open-source Swagger framework.
It allows you to view the operations, parameters, and request and reponse schemas for every resource. Request samples are presented in cURL (Shell) and JavaScript; some samples also include just the JSON object. Response samples are all JSON.
For more information and examples on using the Wowza Streaming Cloud REST API, see our library of Wowza Streaming Cloud REST API technical articles.
Query requirements
The Wowza Streaming Cloud REST API uses HTTP requests to retrieve data from cloud-based servers. Requests must contain proper JSON, two authentication keys, and the correct version number in the base path.
JSON
The Wowza Streaming Cloud REST API uses the JSON API specification to request and return data. This means requests must include the header Content-Type: application/json and must include a single resource object in JSON format as primary data.
Responses include HTTP status codes that indicate whether the query was successful. If there was an error, a description explains the problem so that you can fix it and try again.
Authentication
Requests to the Wowza Streaming Cloud REST API must be authenticated with two keys: an API key and an access key. Each key is a 64-character alphanumeric string that you can find on the API Access page in Wowza Streaming Cloud.
Use the wsc-api-key and wsc-access-key headers to authenticate requests, like this (in cURL):

Other APIs in the same category

Cloud OS Login API

googleapis.com
You can use OS Login to manage access to your VM instances using IAM roles.
Use API

reCAPTCHA Enterprise API

googleapis.com
Use API

My Business Notifications API

googleapis.com
The My Business Notification Settings API enables managing notification settings for business accounts.
Use API

Cloud Video Intelligence API

googleapis.com
Detects objects, explicit content, and scene changes in videos. It also specifies the region for annotation and transcribes speech to text. Supports both asynchronous API and streaming API.
Use API

Google Site Verification API

googleapis.com
Verifies ownership of websites or domains with Google.
Use API

Network Services API

googleapis.com
Use API

Certificate Authority API

googleapis.com
The Certificate Authority Service API is a highly-available, scalable service that enables you to simplify and automate the management of private certificate authorities (CAs) while staying in control of your private keys.
Use API

Cloud Vision API

googleapis.com
Integrates Google Vision features, including image labeling, face, logo, and landmark detection, optical character recognition (OCR), and detection of explicit content, into applications.
Use API

The Noun Project

thenounproject.com
Icons for Everything
Use API

Smart Device Management API

googleapis.com
Allow select enterprise partners to access, control, and manage Google and Nest devices programmatically.
Use API

Tasks API

googleapis.com
The Google Tasks API lets you manage your tasks and task lists.
Use API

Semantic API

nytimes.com
The Semantic API complements the Articles API. With the Semantic API, you get access to the long list of people, places, organizations and other locations, entities and descriptors that make up the controlled vocabulary used as metadata by The New York Times (sometimes referred to as Times Tags and used for Times Topics pages).
The Semantic API uses concepts which are, by definition, terms in The New York Times controlled vocabulary. Like the way facets are used in the Articles API, concepts are a good way to uncover articles of interest in The New York Times archive, and at the same time, limit the scope and number of those articles. The Semantic API maps to external semantic data resources, in a fashion consistent with the idea of linked data. The Semantic API also provides combination and relationship information to other, similar concepts in The New York Times controlled vocabulary.
Use API
⬅ Back to the list of mock samples