---
title: "Add a new version to a branch."
method: POST
path: "/groups/{groupId}/artifacts/{artifactId}/branches/{branchId}/versions"
tags: ["Branches"]
---

# Add a new version to a branch.

`POST /groups/{groupId}/artifacts/{artifactId}/branches/{branchId}/versions`

Add a new version to an artifact branch. Returns a list of version identifiers in the branch, ordered from the latest (tip of the branch) to the oldest.

This operation can fail for the following reasons:
* No artifact with this `groupId` and `artifactId` exists (HTTP error `404`)
* No branch with this `branchId` exists (HTTP error `404`)
* Branch already contains the given version. Artifact branches are append-only, cycles and history rewrites, except by replacing the entire branch using the replaceBranchVersions operation,  are not supported. (HTTP error `409`)
* A server error occurred (HTTP error `500`)

## Request body

- AddVersionToBranch
  - `version` string, required

## Response `204`

The version was successfully added to the branch.

## Other responses

- `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.
- `404` — Common response for all operations that can return a `404` error.
- `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-v3.md) · [All operations](https://skmtc.net/apicurio/apis/apicurio-registry-api-v3/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/apicurio/apicurio-registry-api-v3/revisions/c39cb56d7dbc/schema)