# Fetch transcoder usage summary

(Available from version 1.4) This operation shows a summary of the amount of usage (egress) for all transcoders in the account. The default time frame is from the last billing date to the end of the current day.

Endpoint: GET /usage/transcoders/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: {"egress_bytes":3000,"egress_seconds":300,"configurations":[{"transcoder_type":"transcoded","billing_mode":"pay_as_you_go","egress_bytes":1000,"egress_seconds":200},{"transcoder_type":"passthrough","billing_mode":"twentyfour_seven","egress_bytes":2000,"egress_seconds":100}]}

  - `summary.egress_bytes` (integer)
    The total amount of content, in bytes, that went through all transcoders during the selected time frame.
    Example: 3000

  - `summary.egress_seconds` (integer)
    The total amount of time, in seconds, that it took for all transcoders to be processed.
    Example: 300

  - `summary.configurations` (object)
    Example: [{"transcoder_type":"transcoded","billing_mode":"pay_as_you_go","egress_bytes":1000,"egress_seconds":200},{"transcoder_type":"passthrough","billing_mode":"twentyfour_seven","egress_bytes":2000,"egress_seconds":100}]

  - `summary.configurations.transcoder_type` (string)
    The type of transcoder. The default is transcoded.
    Enum: "transcoded", "passthrough"

  - `summary.configurations.billing_mode` (string)
    The billing mode for the transcoder. The default is pay_as_you_go.

pay_as_you_go — Billed as a single event. A single event is use-based and you incur charges for the time spent streaming.

twentyfour_seven — Billed as a 24x7 channel. A 24x7 channel is unlimited stream time for one channel. This billing mode doesn't incur overages, since it's unlimited.
    Enum: "pay_as_you_go", "twentyfour_seven"

  - `summary.configurations.egress_bytes` (integer)
    The amount of content, in bytes, that went through the transcoder during the selected time frame.

  - `summary.configurations.egress_seconds` (integer)
    The amount of time, in seconds, that it took for the transcoder to be processed.

  - `limits` (object)
    The time frame represented in the response.
    Example: {"from":"2019-02-15T00:00:00.000Z","to":"2019-09-24T00:00:00.000Z"}

  - `limits.from` (string)
    The start of the range of time represented in the response.
    Example: "2019-02-15T00:00:00.000Z"

  - `limits.to` (string)
    The end of the range of time represented in the response.
    Example: "2019-09-24T00: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)