The Hypertext Transfer Protocol (HTTP) allows for storing responses in a cache where the response data can be retrieved when specific API requests are made. Retrieving the response data from the cache, rather than going through the entire request process, can reduce bandwidth, latency, and the load on servers.
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 |
* Cache time applies to GET requests for all endpoints within the resource
