canonical: https://jentic.com/apis/wowza.com/wowza-streaming-cloud-rest-api-reference-documenta # Wowza Streaming Cloud REST API Reference Documentation About the REST API The Wowza Streaming CloudTM 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 . The API exposes 104 endpoints secured with apiKey authentication. ## For AI agents Programmatically fetch swagger information, create a live stream. Covers 104 operations with apiKey authentication. ## Scope Does not handle payments, communications, or crm - use for media and content only. ## Capabilities - Fetch Swagger information - Create a live stream - Update a live stream - Delete a live stream - Regenerate the connection code for a live stream ## Use cases ### Media and Content Operations Use the Wowza Streaming Cloud REST API Reference Documentation to perform media operations programmatically. The API provides 104 endpoints covering core functionality including fetch swagger information, create a live stream, fetch all live streams. Example prompt: Call GET /api/v1/specs to fetch swagger information ### Automated live_streams Management Automate live_streams operations by combining multiple Wowza Streaming Cloud REST API Reference Documentation endpoints. Agents can create a live stream and then fetch all live streams in a single workflow. Example prompt: Call POST /live_streams to create a live stream, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Wowza Streaming Cloud REST API Reference Documentation endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually. Example prompt: Search Jentic for 'fetch swagger information', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /api/v1/specs | Fetch Swagger information | | POST | /live_streams | Create a live stream | | GET | /live_streams | Fetch all live streams | | GET | /live_streams/{id} | Fetch a live stream | | PATCH | /live_streams/{id} | Update a live stream | | DELETE | /live_streams/{id} | Delete a live stream | | PUT | /live_streams/{id}/regenerate_connection_code | Regenerate the connection code for a live stream | | PUT | /live_streams/{id}/reset | Reset a live stream | ## Key resources - **live_streams** — Operations related to live streams. - **players** — Operations related to players, which are created through the /live_streams resource. - **recordings** — Operations related to recordings. - **schedules** — Operations related to schedules. - **stream_sources** — Operations related to stream sources. ## Why Jentic - **Setup:** Wiring the Wowza Streaming Cloud REST API by hand means sending its paired access-key and api-key headers, choosing the sandbox or production host, and managing streams across 104 operations yourself. Through Jentic you install once, import the Wowza Streaming Cloud REST API from the API Directory, store the keys once, and your agent calls it. - **Permission scoping:** The Wowza Streaming Cloud REST API puts the live-stream id in the URL path (/live_streams/{id}), so a rule can pin your agent to one live stream: it can read or reset that stream and nothing else. You choose the operations it may call, so destructive ones like deleting a stream or regenerating a connection code are not included unless you add them. - **Credential handling:** Your Wowza Streaming Cloud access key and API key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a live stream' or 'reset a live stream', and Jentic returns the matching Wowza Streaming Cloud REST API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Cloudinary** — Alternative media API - **Mux** — Alternative media API ## FAQ ### What authentication does the Wowza Streaming Cloud REST API Reference Documentation use? The Wowza Streaming Cloud REST API Reference Documentation uses an API key passed in the `wsc-access-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I fetch swagger information with the Wowza Streaming Cloud REST API Reference Documentation? Yes. Use the GET /api/v1/specs endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Wowza Streaming Cloud REST API Reference Documentation? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I fetch swagger information through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'fetch swagger information'. Jentic returns the matching Wowza Streaming Cloud REST API Reference Documentation operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Wowza Streaming Cloud REST API Reference Documentation have? The Wowza Streaming Cloud REST API Reference Documentation exposes 104 endpoints covering live_streams, players, recordings operations. ### Can I limit what my agent is allowed to do with the Wowza Streaming Cloud API? Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use, and you pick exactly which Wowza Streaming Cloud operations it can call. Since the live-stream id sits in the URL path (/live_streams/{id}), a rule can pin the agent to a single stream so it only reads or resets that one and touches nothing else. Destructive operations such as deleting a live stream or regenerating its connection code are excluded unless you explicitly add them.