List profiles
GET/bv/configuration/v1/profiles
Lists the array of Profile
resource.
Request
Query Parameters
- VIDEO_CODEC_H264: VIDEO_CODEC_H264 Indicates video code H.264
- VIDEO_CODEC_H265: VIDEO_CODEC_H265 Indicates video code H.265
Required. The current page in the current pagination. Need to assign positive number. Min: 1 Max: 100
Required. The number of items per page in the current pagination. Need to assign positive number. Min: 1 Max: 100
Possible values: [VIDEO_CODEC_H264
, VIDEO_CODEC_H265
]
Optional.
Header Parameters
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
- 400
- 401
- 403
- 500
- default
A successful response.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- ]
profiles object[]
Output only. The resource identifier of profile.
Input only. The name of profile.
Possible values: [VIDEO_CODEC_H264
, VIDEO_CODEC_H265
]
Input only. The video codec.
Input only. The video width in pixels.
Input only. The video height in pixels.
Input only. The video bitrate.
Input only. The audio bitrate.
Possible values: [CODEC_PROFILE_AUTO
, CODEC_PROFILE_BASELINE
, CODEC_PROFILE_MAIN
, CODEC_PROFILE_HIGH
, CODEC_PROFILE_MAIN10
]
Input only. H.264/H.265 codec profile.
Possible values: [CODEC_PROFILE_LEVEL_AUTO
, CODEC_PROFILE_LEVEL_1
, CODEC_PROFILE_LEVEL_1_1
, CODEC_PROFILE_LEVEL_1_2
, CODEC_PROFILE_LEVEL_1_3
, CODEC_PROFILE_LEVEL_2
, CODEC_PROFILE_LEVEL_2_1
, CODEC_PROFILE_LEVEL_2_2
, CODEC_PROFILE_LEVEL_3
, CODEC_PROFILE_LEVEL_3_1
, CODEC_PROFILE_LEVEL_3_2
, CODEC_PROFILE_LEVEL_4
, CODEC_PROFILE_LEVEL_4_1
, CODEC_PROFILE_LEVEL_4_2
, CODEC_PROFILE_LEVEL_5
, CODEC_PROFILE_LEVEL_5_1
, CODEC_PROFILE_LEVEL_5_2
, CODEC_PROFILE_LEVEL_6
]
Input only. Specify level for H.264/H.265.
Input only. Enable/Disable B-frame.
Possible values: [FRAME_RATE_10
, FRAME_RATE_15
, FRAME_RATE_23_97
, FRAME_RATE_24
, FRAME_RATE_25
, FRAME_RATE_29_97
, FRAME_RATE_30
, FRAME_RATE_50
, FRAME_RATE_59_94
, FRAME_RATE_60
, FRAME_RATE_SOURCE
]
Input only. The video frame rate.
Input only. GOP size (keyframe interval) in seconds.
Input only. Length of video duration for each segment package in seconds.
Possible values: [RESOLUTION_TYPE_SD
, RESOLUTION_TYPE_HD
, RESOLUTION_TYPE_FHD
, RESOLUTION_TYPE_4K
]
pagination object
Output only. The total numbers of the list in the current pagination.
Output only. The number of items per page in the current pagination.
Output only. The current page in the current pagination.
{
"pagination": {
"current_page": 1,
"items_per_page": 10,
"total_items": 13
},
"profiles": [
{
"audio_bitrate": "24",
"b_frame": true,
"codec_profile": "CODEC_PROFILE_AUTO",
"frame_rate": "FRAME_RATE_SOURCE",
"gop_size": 2,
"id": "aa42c109-da05-4739-b72a-065b8a85dac8",
"level": "CODEC_PROFILE_LEVEL_AUTO",
"name": "eee",
"preset": false,
"segment_duration": 6,
"standard": "RESOLUTION_TYPE_SD",
"video_bitrate": "60",
"video_codec": "VIDEO_CODEC_H264",
"video_height": 800,
"video_width": 800
},
{
"audio_bitrate": "192",
"b_frame": true,
"codec_profile": "CODEC_PROFILE_AUTO",
"frame_rate": "FRAME_RATE_60",
"gop_size": 2,
"id": "77a94c55-57f7-419d-8520-ee288251a748",
"level": "CODEC_PROFILE_LEVEL_AUTO",
"name": "2160p-40Mbps",
"preset": true,
"segment_duration": 6,
"standard": "RESOLUTION_TYPE_4K",
"video_bitrate": "40000",
"video_codec": "VIDEO_CODEC_H264",
"video_height": 2160,
"video_width": 3840
},
{
"audio_bitrate": "192",
"b_frame": true,
"codec_profile": "CODEC_PROFILE_AUTO",
"frame_rate": "FRAME_RATE_30",
"gop_size": 2,
"id": "e11f00a6-9989-4ffe-b685-acea84ab85dd",
"level": "CODEC_PROFILE_LEVEL_AUTO",
"name": "2160p-20Mbps",
"preset": true,
"segment_duration": 6,
"standard": "RESOLUTION_TYPE_4K",
"video_bitrate": "20000",
"video_codec": "VIDEO_CODEC_H264",
"video_height": 2160,
"video_width": 3840
},
{
"audio_bitrate": "128",
"b_frame": true,
"codec_profile": "CODEC_PROFILE_AUTO",
"frame_rate": "FRAME_RATE_60",
"gop_size": 2,
"id": "1024fed8-f8b9-4b54-99b2-85688296638a",
"level": "CODEC_PROFILE_LEVEL_AUTO",
"name": "1080p-10Mbps",
"preset": true,
"segment_duration": 6,
"standard": "RESOLUTION_TYPE_FHD",
"video_bitrate": "10000",
"video_codec": "VIDEO_CODEC_H264",
"video_height": 1080,
"video_width": 1920
},
{
"audio_bitrate": "128",
"b_frame": true,
"codec_profile": "CODEC_PROFILE_AUTO",
"frame_rate": "FRAME_RATE_30",
"gop_size": 2,
"id": "57acf6c4-688e-47c5-a4f9-548c64ef6ddb",
"level": "CODEC_PROFILE_LEVEL_AUTO",
"name": "1080p-5Mbps",
"preset": true,
"segment_duration": 6,
"standard": "RESOLUTION_TYPE_FHD",
"video_bitrate": "5000",
"video_codec": "VIDEO_CODEC_H264",
"video_height": 1080,
"video_width": 1920
},
{
"audio_bitrate": "128",
"b_frame": true,
"codec_profile": "CODEC_PROFILE_AUTO",
"frame_rate": "FRAME_RATE_60",
"gop_size": 2,
"id": "de802259-af85-48bf-8b97-fd6cf304c265",
"level": "CODEC_PROFILE_LEVEL_AUTO",
"name": "720p-5Mbps",
"preset": true,
"segment_duration": 6,
"standard": "RESOLUTION_TYPE_HD",
"video_bitrate": "5000",
"video_codec": "VIDEO_CODEC_H264",
"video_height": 720,
"video_width": 1440
},
{
"audio_bitrate": "128",
"b_frame": true,
"codec_profile": "CODEC_PROFILE_AUTO",
"frame_rate": "FRAME_RATE_30",
"gop_size": 2,
"id": "d8b7caa0-7487-4cdf-ab64-44cf54783d34",
"level": "CODEC_PROFILE_LEVEL_AUTO",
"name": "720p-2.5Mbps",
"preset": true,
"segment_duration": 6,
"standard": "RESOLUTION_TYPE_HD",
"video_bitrate": "2500",
"video_codec": "VIDEO_CODEC_H264",
"video_height": 720,
"video_width": 1440
},
{
"audio_bitrate": "96",
"b_frame": true,
"codec_profile": "CODEC_PROFILE_AUTO",
"frame_rate": "FRAME_RATE_60",
"gop_size": 2,
"id": "8d8477ed-3353-4e45-b6fe-6c7ff2eefee1",
"level": "CODEC_PROFILE_LEVEL_AUTO",
"name": "480p-3Mbps",
"preset": true,
"segment_duration": 6,
"standard": "RESOLUTION_TYPE_SD",
"video_bitrate": "3000",
"video_codec": "VIDEO_CODEC_H264",
"video_height": 480,
"video_width": 850
},
{
"audio_bitrate": "96",
"b_frame": true,
"codec_profile": "CODEC_PROFILE_AUTO",
"frame_rate": "FRAME_RATE_30",
"gop_size": 2,
"id": "39861dab-83da-4cd7-bb58-7ae6af648c19",
"level": "CODEC_PROFILE_LEVEL_AUTO",
"name": "480p-1.5Mbps",
"preset": true,
"segment_duration": 6,
"standard": "RESOLUTION_TYPE_SD",
"video_bitrate": "1500",
"video_codec": "VIDEO_CODEC_H264",
"video_height": 480,
"video_width": 850
},
{
"audio_bitrate": "96",
"b_frame": true,
"codec_profile": "CODEC_PROFILE_AUTO",
"frame_rate": "FRAME_RATE_60",
"gop_size": 2,
"id": "627fb5be-b673-4fe6-876f-efad1d2011e5",
"level": "CODEC_PROFILE_LEVEL_AUTO",
"name": "360p-1.4Mbps",
"preset": true,
"segment_duration": 6,
"standard": "RESOLUTION_TYPE_SD",
"video_bitrate": "1400",
"video_codec": "VIDEO_CODEC_H264",
"video_height": 360,
"video_width": 640
}
]
}
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
- Example (from schema)
Schema
- Array [
- 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.)
- ]
details object[]
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:
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.
{
"code": 0,
"message": "string",
"details": [
{
"@type": "string"
}
]
}
A unauthenticated response.
The header authorization
was missing or unidentified.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- 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.)
- ]
details object[]
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:
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.
{
"code": 0,
"message": "string",
"details": [
{
"@type": "string"
}
]
}
A forbidden response.
It means that the provided authorization
did not have enough permission to access the resource or the API.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- 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.)
- ]
details object[]
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:
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.
{
"code": 0,
"message": "string",
"details": [
{
"@type": "string"
}
]
}
A server error response. There are more HTTP status code mappings listed on here.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- 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.)
- ]
details object[]
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:
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.
{
"code": 0,
"message": "string",
"details": [
{
"@type": "string"
}
]
}
An unexpected error response.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- 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.)
- ]
details object[]
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:
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.
{
"code": 0,
"message": "string",
"details": [
{
"@type": "string"
}
]
}