---
title: "Create a new group"
method: POST
path: "/groups"
tags: ["Groups"]
---

# Create a new group

`POST /groups`

Creates a new group.

This operation can fail for the following reasons:

* A server error occurred (HTTP error `500`)
* The group already exist (HTTP error `409`)
* Invalid group ID (e.g., reserved name 'default') (HTTP error `400`)

## Request body

- CreateGroupMetaData
  - `description` string
  - `properties` Properties — User-defined name-value pairs. Name and value must be strings.
  - `id` string, required

## Response `200`

The group has been successfully created.

- GroupMetaData
  - `id` string, required — An ID of a single artifact group.
  - `description` string, required
  - `createdBy` string, required
  - `createdOn` string, date-time, required
  - `modifiedBy` string, required
  - `modifiedOn` string, date-time, required
  - `properties` Properties, required — User-defined name-value pairs. Name and value must be strings.

## Other responses

- `400` — Common response for all operations that can return a `400` error.
- `401` — Common response for all operations that can return a `401` error indicating authentication is required.
- `403` — Common response for all operations that can return a `403` error indicating the user is authenticated but not authorized.
- `409` — Common response used when an input conflicts with existing data.
- `500` — Common response for all operations that can fail with an unexpected server error.

---

[API](https://skmtc.net/apicurio/apis/apicurio-registry-api-v2.md) · [All operations](https://skmtc.net/apicurio/apis/apicurio-registry-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/apicurio/apicurio-registry-api-v2/versions/f177177d6a5a/schema)