List subtitles by video

GET 
/bv/cms/v1/library/videos/:id/subtitles

List subtitles by video

Request

Path Parameters

id stringrequired

The library id of the video.

Query Parameters

current_page int32

Input only. Indicates the current page to show. Default: 1

items_per_page int32

Input only. Indicates the number of items to show per page. Default: 100.

Header Parameters

x-bv-org-id stringrequired

To invoke this API using api_token, you need to set the x-bv-org-id header to specify the organization for which you want to perform the action.

Responses

200

A successful response.

application/json

Schema

Schema

video_subtitles object[]
Array [
id string
The unique id of subtitle.
track_no string
The number of audio track.
lang_code string
The language code of the subtitle. The format is ISO639-1+ISO-3166-1 (e.g., en-US).
display string
The display name of the subtitle.
vod_id string
The id of VOD. If the video has been encoded, it will provide the vod id for getting vod information.
status string
Possible values: [SUBTITLE_STATUS_GENERATING, SUBTITLE_STATUS_SUCCEED, SUBTITLE_STATUS_FAILED, SUBTITLE_STATUS_NOT_FOUND]
The status of subtitle.
subtitle_file_info object
The information of subtitle.
file object
id string
Output only. The unique id of the file.
type string
Possible values: [FILE_TYPE_VIDEO, FILE_TYPE_IMAGE, FILE_TYPE_SUBTITLE, FILE_TYPE_DOCUMENT, FILE_TYPE_WEB_LINK, FILE_TYPE_AUDIO]
Input only. The type of the file.
name string
Input only. The name of the file.
size int64
Input only. The size of the file in bytes.
uri string
Output only. The uri of the file.
source stringrequired
Possible values: [FILE_SOURCE_LIVE_EVENT, FILE_SOURCE_UPLOAD_IN_LIBRARY, FILE_SOURCE_ADD_VOD, FILE_SOURCE_CLOUD_STORAGE_AWS, FILE_SOURCE_STT, FILE_SOURCE_ADD_AOD, FILE_SOURCE_AISK, FILE_SOURCE_GOOGLE_DRIVE]
Required. The source of the file, only for display.
attrs object
property name* string
has_subtitle Output Only. Indicate the video has subtitle or not when the file type is `FILE_TYPE_VIDEO` (boolean)
subtitles object[]
Array [
id string
The unique id of the subtitle.
library_id string
The unique id of the library subtitle file.
name string
The name of the subtitle file.
code string
The language code of the subtitle file. Follow RFC 5646 (shortest ISO 639 code).
display string
The display name of the subtitle file.
]
status string
Possible values: [FILE_STATUS_SUCCEED, FILE_STATUS_PROGRESSING, FILE_STATUS_FAILED]
Output Only. The file status.
permission object
default_access_role stringrequired
Possible values: [ACCESS_ROLE_DENY, ACCESS_ROLE_SUPER_EDITOR, ACCESS_ROLE_EDITOR, ACCESS_ROLE_VIEWER]
assignments object[]
Array [
id stringrequired
Required. Output Only. if the assigned_type is ASSIGNED_TYPE_USER, the id is user id. if the assigned_type is ASSIGNED_TYPE_GROUP, the id is group id.
email string
Output Only. It will return if the assigned_type matches ASSIGNED_TYPE_USER.
name string
Output Only. The name of user or group.
assigned_type Required. Output Only. It indicates the assigned type is user or group. It is not accept the `ASSIGNED_TYPE_OWNER` (string)required
Possible values: [ASSIGNED_TYPE_USER, ASSIGNED_TYPE_GROUP]
access_role Required. Output Only. It indicates access role. It is not accept the `ACCESS_ROLE_DENY` (string)required
Possible values: [ACCESS_ROLE_DENY, ACCESS_ROLE_SUPER_EDITOR, ACCESS_ROLE_EDITOR, ACCESS_ROLE_VIEWER]
]
created_at date-time
Output only.
updated_at date-time
Output only.
contents object[]
Array [
index int32
start_at string
end_at string
words string[]
]
source_type string
Possible values: [SUBTITLE_SOURCE_TYPE_LOCAL, SUBTITLE_SOURCE_TYPE_STT]
The source type of subtitle.
created_at date-time
Output only.
updated_at date-time
Output only.
]
pagination object

total_items int32

Output only. The total numbers of the list in the current pagination.

items_per_page int32

Output only. The number of items per page in the current pagination.

current_page int32

Output only. The current page in the current pagination.

Example (from schema)

{
  "video_subtitles": [
    {
      "id": "string",
      "track_no": "string",
      "lang_code": "string",
      "display": "string",
      "vod_id": "string",
      "status": "SUBTITLE_STATUS_GENERATING",
      "subtitle_file_info": {
        "file": {
          "id": "string",
          "type": "FILE_TYPE_VIDEO",
          "name": "string",
          "size": "string",
          "uri": "string",
          "source": "FILE_SOURCE_LIVE_EVENT",
          "attrs": {},
          "has_subtitle": true,
          "subtitles": [
            {
              "id": "string",
              "library_id": "string",
              "name": "string",
              "code": "string",
              "display": "string"
            }
          ],
          "status": "FILE_STATUS_SUCCEED",
          "permission": {
            "assignments": [
              {
                "access_role": "ACCESS_ROLE_SUPER_EDITOR",
                "assigned_type": "ASSIGNED_TYPE_OWNER",
                "email": "",
                "id": "",
                "name": ""
              }
            ],
            "default_access_role": "ACCESS_ROLE_DENY"
          },
          "created_at": "2024-05-20T05:01:36.599Z",
          "updated_at": "2024-05-20T05:01:36.599Z"
        },
        "contents": [
          {
            "index": 0,
            "start_at": "string",
            "end_at": "string",
            "words": [
              "string"
            ]
          }
        ]
      },
      "source_type": "SUBTITLE_SOURCE_TYPE_LOCAL",
      "created_at": "2024-05-20T05:01:36.599Z",
      "updated_at": "2024-05-20T05:01:36.599Z"
    }
  ],
  "pagination": {
    "total_items": 0,
    "items_per_page": 0,
    "current_page": 0
  }
}

400

A bad request response. The code is 3 means got an invalid argument. There are more HTTP status code mappings listed on here and gRPC code on here.

application/json

Schema

Schema

code int32
message string
details object[]
Array [
@type string
A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in path/google.protobuf.Duration). The name should be in a canonical form (e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme http, https, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows:
• If no scheme is provided, https is assumed.
• An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
• Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one.
Schemes other than http, https (or the empty scheme) might be used with implementation specific semantics.
]

Example (from schema)

{
  "code": 0,
  "message": "string",
  "details": [
    {
      "@type": "string"
    }
  ]
}

401

A unauthenticated response. The header authorization was missing or unidentified.

application/json

Schema

Schema

code int32
message string
details object[]
Array [
@type string
A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in path/google.protobuf.Duration). The name should be in a canonical form (e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme http, https, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows:
• If no scheme is provided, https is assumed.
• An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
• Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one.
Schemes other than http, https (or the empty scheme) might be used with implementation specific semantics.
]

Example (from schema)

{
  "code": 0,
  "message": "string",
  "details": [
    {
      "@type": "string"
    }
  ]
}

403

A forbidden response. It means that the provided authorization did not have enough permission to access the resource or the API.

application/json

Schema

Schema

code int32
message string
details object[]
Array [
@type string
A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in path/google.protobuf.Duration). The name should be in a canonical form (e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme http, https, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows:
• If no scheme is provided, https is assumed.
• An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
• Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one.
Schemes other than http, https (or the empty scheme) might be used with implementation specific semantics.
]

Example (from schema)

{
  "code": 0,
  "message": "string",
  "details": [
    {
      "@type": "string"
    }
  ]
}

500

A server error response. There are more HTTP status code mappings listed on here.

application/json

Schema

Schema

code int32
message string
details object[]
Array [
@type string
A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in path/google.protobuf.Duration). The name should be in a canonical form (e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme http, https, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows:
• If no scheme is provided, https is assumed.
• An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
• Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one.
Schemes other than http, https (or the empty scheme) might be used with implementation specific semantics.
]

Example (from schema)

{
  "code": 0,
  "message": "string",
  "details": [
    {
      "@type": "string"
    }
  ]
}

default

An unexpected error response.

application/json

Schema

Schema

code int32
message string
details object[]
Array [
@type string
A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in path/google.protobuf.Duration). The name should be in a canonical form (e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme http, https, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows:
• If no scheme is provided, https is assumed.
• An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
• Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one.
Schemes other than http, https (or the empty scheme) might be used with implementation specific semantics.
]

Example (from schema)

{
  "code": 0,
  "message": "string",
  "details": [
    {
      "@type": "string"
    }
  ]
}

Loading...