The streaming endpoint is the origin that packages and delivers media content to viewers. Each RMS account includes one streaming endpoint, shared across all live events and on-demand assets.
In this article:
Concept
When a viewer requests content, the streaming endpoint converts stored MP4 files into HLS or MPEG-DASH format on request. This process, dynamic packaging, happens at delivery time without storing multiple format copies. The same endpoint serves both live streams and on-demand content.
The streaming endpoint in RMS is always running. There is no start or stop process - it is managed automatically as part of your RMS account.
Getting your hostname
The hostname is the delivery domain used to build playback URLs. Retrieve it once - from the RMS Console under Settings > Service Connections > Streaming Endpoints, or programmatically via the [Get Streaming Endpoint API], where properties.hostName returns the configured value.
The value reflects your current delivery configuration - by default, your Front Door domain, or a custom domain if one has been set up.
The hostname is the base of all playback URLs, whether you're serving on-demand content or a live stream. For a step-by-step example using a live stream, see Live streaming quickstart.
API operations
RMS supports two read operations on streaming endpoints. Both return the full AMS-compatible response structure - properties.hostName is the value your application needs to build playback URLs. The remaining response fields are present for API compatibility.
Not implemented
The following operations exist for AMS API compatibility but return HTTP 501 in RMS:
| Method | Operation |
| PUT | Create streaming endpoint. |
| PATCH | Update streaming endpoint. |
| DELETE | Delete streaming endpoint. |
| POST | Stop streaming endpoint. |
| POST | Scale streaming endpoint. |