Update subtitles of VOD

PUT 
https://api.one.blendvision.com/bv/cms/v1/vods/:id/subtitles

Modifies the subtitles of a VOD resource with the specified subtitle file.

---

Required field(s):

• id

---

Request

Path Parameters

id stringrequired

Required. The unique id of the VOD resource.

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.

application/json

Body

required

subtitles object[]
Optional. The subtitles that will be added to the VOD resource.
Array [
id stringrequired
The unique id of the library subtitle file.
name string
The name of the subtitle file.
code string
The language code of the subtitle. The format is ISO639-1+ISO-3166-1 (e.g., en-US).
display stringrequired
The display name of the subtitle file.
translate_settings object[]
The translate settings of the subtitle. It's only supported in AddVODSubtitles, TranslateVODSubtitle and CreateVOD API.
Array [
source_lang_code stringrequired
The language code of the source subtitle file. The format is ISO639-1+ISO-3166-1 (e.g., en-US).
target_lang_code stringrequired
The target language code you want to translate into. The format is ISO639-1+ISO-3166-1 (e.g., en-US).
display stringrequired
The display name of the translated subtitle file.
]
]
stt_subtitles object[]
Optional. The subtitle will auto-generated and added to VOD resource.
Array [
track_no string
The number of audio track.
lang_code string
The language code of the subtitle file. The format is ISO639-1+ISO-3166-1 (e.g., en-US).
display stringrequired
The display name of the subtitle file.
translate_settings object[]
The translate settings of the subtitle. It's only supported in AddVODSubtitles, TranslateVODSubtitle and CreateVOD API.
Array [
source_lang_code stringrequired
The language code of the source subtitle file. The format is ISO639-1+ISO-3166-1 (e.g., en-US).
target_lang_code stringrequired
The target language code you want to translate into. The format is ISO639-1+ISO-3166-1 (e.g., en-US).
display stringrequired
The display name of the translated subtitle file.
]
]

Responses

200

A successful response.

application/json

Schema

Schema

object

Example (from schema)

{}

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"
    }
  ]
}

Authorization: authorization

name: authorizationtype: apiKeydescription: Enter the token with Bearer schema prefix, eg. `Bearer <token-string>`in: header

• curl
• python
• go
• nodejs
• php

• CURL

curl -L -X PUT 'https://api.one.blendvision.com/bv/cms/v1/vods/:id/subtitles' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-H 'authorization: <API_KEY_VALUE>' \
-d '{
  "stt_subtitles": [
    {
      "display": "English",
      "lang_code": "en",
      "track_no": "0"
    }
  ],
  "subtitles": [
    {
      "code": "en",
      "display": "English",
      "id": "34386ef5-209e-453f-93c7-6f48a24ad38c",
      "name": "english.srt"
    },
    {
      "code": "zh",
      "display": "Chinese",
      "id": "daedaa0c-6250-4637-965e-c70c24568c73",
      "name": "chinese.vtt"
    }
  ]
}'

Request Collapse all

Base URL

https://api.one.blendvision.com

Auth

BearerTokenAuth

Parameters

id — pathrequired

x-bv-org-id — headerrequired

Body required

{
  "stt_subtitles": [
    {
      "display": "English",
      "lang_code": "en",
      "track_no": "0"
    }
  ],
  "subtitles": [
    {
      "code": "en",
      "display": "English",
      "id": "34386ef5-209e-453f-93c7-6f48a24ad38c",
      "name": "english.srt"
    },
    {
      "code": "zh",
      "display": "Chinese",
      "id": "daedaa0c-6250-4637-965e-c70c24568c73",
      "name": "chinese.vtt"
    }
  ]
}

ResponseClear

Click the Send API Request button above and see the response here!