# Fetch real-time stream usage summary (Available from version 1.11) This operation returns a summary of CDN usage for all real-time streams in the account. Endpoint: GET /usage/real_time_streams/summary Version: v2.0 ## Query parameters: - `from` (string) The start of the range of time you want to view. Specify YYYY-MM-DD HH:00:00 where HH is a 24-hour clock in UTC. The range doesn't include minutes and seconds and rounds minutes up to the hour. The maximum difference between from and to is 90 days. If you set the from query parameter without setting the to query parameter, the data returned will reflect 90 days starting at the from date, or data up to to the current day, whichever is shorter. You can also specify last_bill_date. Default: last billing date - `to` (string) The end of the range of time you want to view. Specify YYYY-MM-DD HH:00:00 where HH is a 24-hour clock in UTC. The range doesn't include minutes and seconds and rounds minutes up to the hour. The maximum difference between from and to is 90 days. If you set the to query parameter without setting the from query parameter, the data returned will be from the past 90 days or from your last invoice date, whichever is shorter. You can also specify last_bill_date. Default: end of the current day ## Response 200 fields (application/json): - `summary` (object) Example: {"bytes_in":987467984710,"bytes_out":1583413248468} - `summary.bytes_in` (integer) The amount of content, in bytes, that came from a video source in to Wowza Video during the selected time frame. Example: 987467984710 - `summary.bytes_out` (integer) The amount of content, in bytes, that went to a viewer during the selected time frame. Example: 1583413248468 - `limits` (object) The time frame represented in the response. Example: {"from":"2023-05-07T00:00:00.000Z","to":"2023-05-26T00:00:00.000Z"} - `limits.from` (string) The start of the range of time represented in the response. Example: "2023-05-07T00:00:00.000Z" - `limits.to` (string) The end of the range of time represented in the response. Example: "2023-05-26T00:00:00.000Z" ## Response 401 fields (application/json): - `meta` (object, required) - `meta.status` (integer) - `meta.code` (string) - `meta.title` (string) - `meta.message` (string) - `meta.description` (string) - `meta.links` (array) ## Response 403 fields (application/json): - `meta` (object, required) - `meta.status` (integer) - `meta.code` (string) - `meta.title` (string) - `meta.message` (string) - `meta.description` (string) - `meta.links` (array) ## Response 404 fields (application/json): - `meta` (object, required) - `meta.status` (integer) - `meta.code` (string) - `meta.title` (string) - `meta.message` (string) - `meta.description` (string) - `meta.links` (array) ## Response 410 fields (application/json): - `meta` (object, required) - `meta.status` (integer) - `meta.code` (string) - `meta.title` (string) - `meta.message` (string) - `meta.description` (string) - `meta.links` (array) ## Response 422 fields (application/json): - `meta` (object, required) - `meta.status` (integer) - `meta.code` (string) - `meta.title` (string) - `meta.message` (string) - `meta.description` (string) - `meta.links` (array)