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

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

Community API

Get access to comments from registered users on New York Times articles. NOTE: This API is deprecated.

Business Profile Performance API

The Business Profile Performance API allows merchants to fetch performance reports about their business profile on Google.

My Business Q&A API

The My Business Q&A API allows questions and answers to be posted for specific listings.

The Noun Project

Icons for Everything

Instagram API

Description of Instagram RESTful API.
Current limitations:
Instagram service does not support cross origin headers
for security reasons, therefore it is not possible to use Swagger UI and make API calls directly from browser.
Modification API requests (POST, DELETE) require additional security scopes
that are available for Apps created on or after Nov 17, 2015 and
started in Sandbox Mode.
Consider the Instagram limitations for API calls that depends on App Mode.
Warning: For Apps created on or after Nov 17, 2015 API responses
containing media objects no longer return the data field in comments and likes nodes.
Last update: 2015-11-28

Workflow Executions API

Execute workflows created with Workflows API.

Spotify Web API

Jellyfin API

jellyfin.local

Apigee Registry API

Spinitron v2 API

spinitron.com
Notes
Tutorial demo using this API is at https://spinitron.com/v2-api-demo/. For web integration using iframes and/or JavaScript instead of an API, see https://spinitron.github.io/v2-web-integration/.
Your API key is found in the Spinitron web app. Log in to Spinitron and go to Automation & API in the Admin menu.
Authenticate by presenting your API key using either HTTP Bearer Authorization
(preferred)
curl -H 'Authorization: Bearer YOURAPIKEY' 'https://spinitron.com/api/spins'
or in the query parameter access-token (less secure owing to webserver
log files)
curl 'https://spinitron.com/api/spins?access-token=YOURAPIKEY'
Limit per page of results is 20 by default and miximally 200.
Try it out below works to
generate example cURL requests but not to get responses from Spinitron. We
do not accept queries sent from web browsers. Copy-paste the cURL commands
and run them from your computer.
Cache the data you get from the API if you are using it in web or mobile integration. It's not ok to query the API on every page request you serve. The demo shows how easy it can be to implement a file cache.
An extension to this API with access to all stations for partner applications is available. Contact us.
An API to manage the running of batch jobs on Google Cloud Platform.

Rotten Tomatoes

Test our API services using I/O Docs.