Automate Wowza Streaming Cloud Reference Documentation
HumDay reads Wowza Streaming Cloud Reference Documentation’s own published API description and derives 100 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Wowza Streaming Cloud Reference Documentation is
# 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 feature
API host: api-sandbox.cloud.wowza.com
What HumDay can do in Wowza Streaming Cloud Reference Documentation
50 documented operations change something in Wowza Streaming Cloud Reference Documentation.
- POSTCreate a schedule
/schedules - POSTCreate a transcoder
/transcoders - POSTCreate a live stream
/live_streams - POSTAdd a stream source
/stream_sources - POSTCreate a stream target
/stream_targets - DELETEDelete a schedule
/schedules/{id} - PATCHUpdate a schedule
/schedules/{id} - PUTEnable a schedule
/schedules/{id}/enable - PUTDisable a schedule
/schedules/{id}/disable - POSTCreate a player URL
/players/{player_id}/urls - POSTCreate an output
/transcoders/{transcoder_id}/outputs - POSTCreate a property for a transcoder
/transcoders/{transcoder_id}/properties - POSTCreate geo-blocking for a stream target
/stream_targets/{stream_target_id}/geoblock - POSTCreate a property for a stream target
/stream_targets/{stream_target_id}/properties - POSTCreate token authorization for a stream target
/stream_targets/{stream_target_id}/token_auth - PATCHUpdate a player
/players/{id} - DELETEDelete a recording
/recordings/{id} - DELETEDelete a transcoder
/transcoders/{id} - PATCHUpdate a transcoder
/transcoders/{id} - DELETEDelete a live stream
/live_streams/{id} - PATCHUpdate a live stream
/live_streams/{id} - DELETEDelete a stream source
/stream_sources/{id} - PATCHUpdate a stream source
/stream_sources/{id} - DELETEDelete a stream target
/stream_targets/{id} - PATCHUpdate a stream target
/stream_targets/{id} - POSTRebuild player code
/players/{id}/rebuild - PUTStop a transcoder
/transcoders/{id}/stop - PUTStop a live stream
/live_streams/{id}/stop - PUTReset a transcoder
/transcoders/{id}/reset - PUTStart a transcoder
/transcoders/{id}/start - PUTReset a live stream
/live_streams/{id}/reset - PUTStart a live stream
/live_streams/{id}/start - PATCHUpdate geo-blocking for a stream target
/stream_targets/{stream_target_id}/geoblock - PUTEnable a transcoder's stream targets
/transcoders/{id}/enable_all_stream_targets - PUTDisable a transcoder's stream targets
/transcoders/{id}/disable_all_stream_targets - PUTRegenerate the connection code for a live stream
/live_streams/{id}/regenerate_connection_code - PATCHUpdate token authorization for a stream target
/stream_targets/{stream_target_id}/token_auth - PUTRegenerate the connection code for a stream target
/stream_targets/{id}/regenerate_connection_code - DELETEDelete a player URL
/players/{player_id}/urls/{id} - PATCHUpdate a player URL
/players/{player_id}/urls/{id} - POSTCreate an output stream target
/transcoders/{transcoder_id}/outputs/{output_id}/output_stream_targets - DELETEDelete an output
/transcoders/{transcoder_id}/outputs/{id} - PATCHUpdate an output
/transcoders/{transcoder_id}/outputs/{id} - DELETEDelete a transcoder's property
/transcoders/{transcoder_id}/properties/{id} - DELETEDelete a stream target property
/stream_targets/{stream_target_id}/properties/{id} - DELETEDelete an output stream target
/transcoders/{transcoder_id}/outputs/{output_id}/output_stream_targets/{stream_target_id} - PATCHUpdate an output stream target
/transcoders/{transcoder_id}/outputs/{output_id}/output_stream_targets/{stream_target_id} - PUTEnable an output stream target
/transcoders/{transcoder_id}/outputs/{output_id}/output_stream_targets/{stream_target_id}/enable - PUTDisable an output stream target
/transcoders/{transcoder_id}/outputs/{output_id}/output_stream_targets/{stream_target_id}/disable - PUTRestart an output stream target
/transcoders/{transcoder_id}/outputs/{output_id}/output_stream_targets/{stream_target_id}/restart
What HumDay can read from Wowza Streaming Cloud Reference Documentation
These are the operations a schedule or a trigger can watch.
- GETFetch a schedule
/schedules/{id} - GETFetch all players
/players - GETFetch all schedules
/schedules - GETFetch all recordings
/recordings - GETFetch all transcoders
/transcoders - GETFetch all live streams
/live_streams - GETFetch all stream sources
/stream_sources - GETFetch all stream targets
/stream_targets - GETFetch the state of a schedule
/schedules/{id}/state - GETFetch all uptime records for a transcoder
/transcoders/{transcoder_id}/uptimes - GETFetch a player
/players/{id} - GETFetch a recording
/recordings/{id} - GETFetch a transcoder
/transcoders/{id} - GETFetch Swagger information
/api/v1/specs - GETFetch a live stream
/live_streams/{id} - GETFetch a stream source
/stream_sources/{id} - GETFetch a stream target
/stream_targets/{id} - GETFetch stream processing time
/usage/time/transcoders - GETFetch network usage for all transcoders
/usage/network/transcoders - GETFetch network usage for all stream sources
/usage/network/stream_sources - GETFetch network usage for all stream targets
/usage/network/stream_targets - GETFetch peak recording storage
/usage/storage/peak_recording - GETFetch an uptime record
/transcoders/{transcoder_id}/uptimes/{id} - GETFetch the state of a player
/players/{id}/state - GETFetch the state of a recording
/recordings/{id}/state - GETFetch the state and uptime ID of a transcoder
/transcoders/{id}/state - GETFetch statistics for a current transcoder
/transcoders/{id}/stats - GETFetch the state of a live stream
/live_streams/{id}/state - GETFetch metrics for an active live stream
/live_streams/{id}/stats - GETFetch all player URLs
/players/{player_id}/urls - GETFetch transcoder's schedules
/transcoders/{id}/schedules - GETFetch a transcoder's recordings
/transcoders/{id}/recordings - GETFetch the thumbnail URL of a transcoder
/transcoders/{id}/thumbnail_url - GETFetch the thumbnail URL of a live stream
/live_streams/{id}/thumbnail_url - GETFetch all outputs of a transcoder
/transcoders/{transcoder_id}/outputs - GETFetch a transcoder's properties
/transcoders/{transcoder_id}/properties - GETFetch geo-blocking for a stream target
/stream_targets/{stream_target_id}/geoblock - GETFetch all properties of a stream target
/stream_targets/{stream_target_id}/properties - GETFetch token authorization for a stream target
/stream_targets/{stream_target_id}/token_auth - GETFetch current health metrics for an active Wowza ultra low latency stream target
/stream_targets/{id}/metrics/current - GETFetch historic health metrics for a Wowza ultra low latency stream target
/stream_targets/{id}/metrics/historic - GETFetch viewer data for a stream target
/usage/viewer_data/stream_targets/{id} - GETFetch a player URL
/players/{player_id}/urls/{id} - GETFetch an output
/transcoders/{transcoder_id}/outputs/{id} - GETFetch a property for a transcoder
/transcoders/{transcoder_id}/properties/{id} - GETFetch a property of a stream target
/stream_targets/{stream_target_id}/properties/{id} - GETFetch all output stream targets of an output of a transcoder
/transcoders/{transcoder_id}/outputs/{output_id}/output_stream_targets - GETFetch current stream health metrics for an active transcoder
/transcoders/{transcoder_id}/uptimes/{id}/metrics/current - GETFetch historic stream health metrics for a transcoder
/transcoders/{transcoder_id}/uptimes/{id}/metrics/historic - GETFetch an output stream target
/transcoders/{transcoder_id}/outputs/{output_id}/output_stream_targets/{stream_target_id}
How automating Wowza Streaming Cloud Reference Documentation works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Wowza Streaming Cloud Reference Documentation account.
- Grant access, then go live. You approve the specific Wowza Streaming Cloud Reference Documentation operations it may use — and only those.
Popular Wowza Streaming Cloud Reference Documentation integrations
Connect Wowza Streaming Cloud Reference Documentation to the tools people pair it with most.
- Wowza Streaming Cloud Reference Documentation and OData for namespace microsoft.graphintegration
- Wowza Streaming Cloud Reference Documentation and Cloudflareintegration
- Wowza Streaming Cloud Reference Documentation and NetBoxintegration
- Wowza Streaming Cloud Reference Documentation and GitHubintegration
- Wowza Streaming Cloud Reference Documentation and Mistintegration
- Wowza Streaming Cloud Reference Documentation and Loket.nlintegration
- Wowza Streaming Cloud Reference Documentation and Atlassian The Jira Cloud platformintegration
- Wowza Streaming Cloud Reference Documentation and Magento B2Bintegration
- Wowza Streaming Cloud Reference Documentation and Stripeintegration
- Wowza Streaming Cloud Reference Documentation and Zuora Reference Billingintegration
- Wowza Streaming Cloud Reference Documentation and bunqintegration
- Wowza Streaming Cloud Reference Documentation and DocuSignintegration
Automate Wowza Streaming Cloud Reference Documentation with these
- Google Compute Engine694 operations
- Jellyfin379 operations
- OpenAI273 operations
- Evetech EVE Swagger Interface206 operations
- Google Campaign Manager 360205 operations
- Google Content for Shopping175 operations
- Google Display & Video 360151 operations
- Bungie.Net134 operations
- VocaDbWeb127 operations
- Google Admin SDK122 operations
- Google Apigee109 operations
- Shutterstock Explorer109 operations
Categories
Questions about Wowza Streaming Cloud Reference Documentation automation
- Can HumDay connect to Wowza Streaming Cloud Reference Documentation?
- Yes. HumDay reads Wowza Streaming Cloud Reference Documentation's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 100 operations are documented.
- Do I need to write code to automate Wowza Streaming Cloud Reference Documentation?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Wowza Streaming Cloud Reference Documentation account.
- What can HumDay do in Wowza Streaming Cloud Reference Documentation?
- 50 of the 100 documented operations change something in Wowza Streaming Cloud Reference Documentation, and 50 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Wowza Streaming Cloud Reference Documentation account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Wowza Streaming Cloud Reference Documentation is held behind that approval.
Where this came from
The operations above are read from a published API description for Wowza Streaming Cloud Reference Documentation at sandbox.cloud.wowza.com/en/docs/api/v1. Descriptions are the provider’s own words, not ours. Last published 2017-11-25.