Wowza Video REST API server response caching
Some Wowza Video REST API endpoints return a cached response if you make
a duplicate GET request to the endpoint within a specified period of
time. We recommend you make requests to these endpoints no more
frequently than the specified cache time, since the data returned will
be unchanged.
The following table shows specific endpoints and the amount of time
responses are cached for GET requests to that endpoint.
| Endpoint | Cache time (seconds) |
|---|---|
| /assets/* | 1 |
| /assets_tags | 1 |
| /live_streams | 1 |
| /live_streams/state | 1 |
| /recordings | 1 |
| /schedules | 1 |
| /stream_sources | 1 |
| /stream_targets | 1 |
| /transcoders | 1 |
| /transcoders/state | 1 |
| /metrics/* | 5 |
| /transcoders/ID/uptimes/ID/metrics/current | 5 |
| /transcoders/ID/uptimes/ID/metrics/historic | 5 |
| /live_streams/ID/stats | 10 |
| /transcoders/ID/stats | 10 |
| /usage/* Exception: /usage/*/live | 60 1 |
| /analytics/viewers/* | 10 - If the time range queried is less than 60 minutes. 60 - If the time range queried is 60 minutes or greater. |
| /analytics/engagement/vod_streams/{id} | 10 - If the time range queried is less than 60 minutes. 60 - If the time range queried is 60 minutes or greater. |
| /analytics/popularity/* | 10 - If the time range queried is less than 60 minutes. 60 - If the time range queried is 60 minutes or greater. |
* Cache time applies to GET requests for all endpoints within the resource