# Fetch a transcoder's recordings Deprecated in 2.0. This operation shows limited details of all of the recordings for a specific transcoder. For detailed information about a recording, use the recording ID to fetch a recording. Endpoint: GET /transcoders/{id}/recordings Version: v2.0 ## Path parameters: - `id` (string, required) The unique alphanumeric string that identifies the transcoder. ## Response 200 fields (application/json): - `recordings` (array, required) Array of recordings of this transcoder. See /recordings for more details. - `recordings.created_at` (string) The date and time that the recording was created. Example: "2020-01-29T17:16:21.993Z" - `recordings.id` (string) The unique alphanumeric string that identifies the recording. Example: "4Jjzstdt" - `recordings.asset_id` (string) Only applies to recordings created for Asset Management. The id for the asset associated with your recording. You can manage your asset in Asset Management. Example: "tk1plmzr" - `recordings.file_name` (string) The file name of the recording. Note: To avoid file management issues in storage, Wowza Video removes or replaces special characters in file names. - `recordings.real_time_stream_id` (string) Only applies to Real-Time Streaming at Scale. The unique alphanumeric string that identifies the real-time stream that was recorded. Example: "cj39nmrt" - `recordings.reason` (string) The reason that a recording has the state failed. - `recordings.state` (string) The state of the recording. Enum: "uploading", "converting", "removing", "completed", "failed" - `recordings.transcoder_id` (string) The unique alphanumeric string that identifies the transcoder that was recorded. Example: "bjaplmrw" - `recordings.updated_at` (string) The date and time that the recording was updated. Example: "2020-01-31T14:14:01.993Z" ## 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)