# Create a new VDBGroup.

Endpoint: POST /vdb-groups
Version: 3.17.0
Security: ApiKeyAuth

## Security:

  - `ApiKeyAuth` (unknown)
    apiKey in header Authorization

## Request body:

  - `application/json` (unknown)
    The parameters to create a VDBGroup.

## Request fields (application/json):

  - `name` (string, required)

  - `vdb_ids` (array)

  - `vdbs` (array)
    Dictates order of operations on VDBs. Operations can be performed in parallel  for all VDBs or sequentially. Below are possible valid and invalid orderings given an example  VDB group with 3 vdbs (A, B, and C). Valid: {"vdb_id":"vdb-1", "order":"1"} {"vdb_id":"vdb-2", order:"1"} {vdb_id:"vdb-3", order:"1"} (parallel) {vdb_id:"vdb-1", order:"1"} {vdb_id:"vdb-2", order:"2"} {vdb_id:"vdb-3", order:"3"} (sequential) Invalid: {vdb_id:"vdb-1", order:"A"} {vdb_id:"vdb-2", order:"B"} {vdb_id:"vdb-3", order:"C"} (sequential) In the sequential case the vdbs with priority 1 is the first to be started and the last to be stopped. This value is set on creation of VDB groups.

  - `vdbs.vdb_id` (string)
    Vdb id

  - `vdbs.order` (integer)
    Dictates order of operations on VDBs. Operations can be performed in parallel  for all VDBs or sequentially. Below are possible valid and invalid orderings given an example  VDB group with 3 vdbs (A, B, and C). Valid: {"vdb_id":"vdb-1", "order":"1"} {"vdb_id":"vdb-2", order:"1"} {vdb_id:"vdb-3", order:"1"} (parallel) {vdb_id:"vdb-1", order:"1"} {vdb_id:"vdb-2", order:"2"} {vdb_id:"vdb-3", order:"3"} (sequential) Invalid: {vdb_id:"vdb-1", order:"A"} {vdb_id:"vdb-2", order:"B"} {vdb_id:"vdb-3", order:"C"} (sequential) In the sequential case the vdbs with priority 1 is the first to be started and the last to be stopped. This value is set on creation of VDB groups.

  - `tags` (array)
    The tags to be created for VDB Group.

  - `tags.key` (string, required)
    Key of the tag
    Example: key-1

  - `tags.value` (string, required)
    Value of the tag
    Example: value-1

  - `make_current_account_owner` (boolean)
    Whether the account creating this VDB group must be configured as owner of the VDB group.

## Response 201:

  - `201` (unknown)
    VDBGroup Created.

## Response 201 fields (application/json):

  - `vdb_group` (object)
    A collection of virtual databases and datesets.

  - `vdb_group.id` (string, required)
    A unique identifier for the entity.
    Example: 123

  - `vdb_group.name` (string, required)
    A unique name for the entity.
    Example: my-first-vdb-group

  - `vdb_group.vdb_ids` (array)
    The list of VDB IDs in this VDBGroup.
    Example: ["vdb-123","vdb-456"]

  - `vdb_group.is_locked` (boolean)
    Indicates whether the VDBGroup is locked.
    Example: false

  - `vdb_group.locked_by` (integer)
    The Id of the account that locked the VDBGroup.
    Example: 1

  - `vdb_group.locked_by_name` (string)
    The name of the account that locked the VDBGroup.
    Example: admin

  - `vdb_group.vdb_group_source` (string)
    Source of the vdb group, default is DCT. In case of self-service container, this value would be ENGINE.
    Enum: "DCT", "ENGINE"

  - `vdb_group.ss_data_layout_id` (string)
    Data-layout Id for engine-managed vdb groups.

  - `vdb_group.vdbs` (array)
    Dictates order of operations on VDBs. Operations can be performed in parallel  for all VDBs or sequentially. Below are possible valid and invalid orderings given an example  VDB group with 3 vdbs (A, B, and C). Valid: {"vdb_id":"vdb-1", "order":"1"} {"vdb_id":"vdb-2", order:"1"} {vdb_id:"vdb-3", order:"1"} (parallel) {vdb_id:"vdb-1", order:"1"} {vdb_id:"vdb-2", order:"2"} {vdb_id:"vdb-3", order:"3"} (sequential) Invalid: {vdb_id:"vdb-1", order:"A"} {vdb_id:"vdb-2", order:"B"} {vdb_id:"vdb-3", order:"C"} (sequential) In the sequential case the vdbs with priority 1 is the first to be started and the last to be stopped. This value is set on creation of VDB groups.

  - `vdb_group.vdbs.vdb_id` (string)
    Vdb id

  - `vdb_group.vdbs.order` (integer)
    Dictates order of operations on VDBs. Operations can be performed in parallel  for all VDBs or sequentially. Below are possible valid and invalid orderings given an example  VDB group with 3 vdbs (A, B, and C). Valid: {"vdb_id":"vdb-1", "order":"1"} {"vdb_id":"vdb-2", order:"1"} {vdb_id:"vdb-3", order:"1"} (parallel) {vdb_id:"vdb-1", order:"1"} {vdb_id:"vdb-2", order:"2"} {vdb_id:"vdb-3", order:"3"} (sequential) Invalid: {vdb_id:"vdb-1", order:"A"} {vdb_id:"vdb-2", order:"B"} {vdb_id:"vdb-3", order:"C"} (sequential) In the sequential case the vdbs with priority 1 is the first to be started and the last to be stopped. This value is set on creation of VDB groups.

  - `vdb_group.vdbs.vdb_name` (string)

  - `vdb_group.vdbs.last_refresh_time_with_group_refresh` (string)
    The last time the VDB was successfully refreshed as a part of VDBGroup refresh operation in UTC timezone.
    Example: 2022-05-29T15:00:00.000Z

  - `vdb_group.database_type` (string)
    The database type of the VDBGroup. If all VDBs in the group are of the same database_type, this field will be set to that type. If the VDBs are of different database_type, this field will be set to 'Mixed'.
    Example: Oracle

  - `vdb_group.status` (string)
    The status of the VDBGroup. If all VDBs in the VDBGroup have the same status, this field will be set to that status. If the VDBs have different statuses, this field will be set to 'Mixed'.
    Example: RUNNING

  - `vdb_group.last_successful_refresh_to_bookmark_id` (string)
    The bookmark ID to which the VDBGroup was last successfully refreshed.
    Example: bookmark-123

  - `vdb_group.last_successful_refresh_time` (string)
    The time at which the VDBGroup was last successfully refreshed.
    Example: 2021-05-01T08:51:34.148Z

  - `vdb_group.tags` (array)

  - `vdb_group.tags.key` (string, required)
    Key of the tag
    Example: key-1

  - `vdb_group.tags.value` (string, required)
    Value of the tag
    Example: value-1