---
title: "Add new Workload Profile Chart Version"
method: POST
path: "/orgs/{orgId}/workload-profile-chart-versions"
tags: ["public", "WorkloadProfile"]
---

# Add new Workload Profile Chart Version

`POST /orgs/{orgId}/workload-profile-chart-versions`

Creates a Workload Profile Chart Version from the uploaded Helm chart. The name and version is retrieved from the chart's metadata (Charts.yaml file).

The request has content type `multipart/form-data` and the request body includes one part:

1. `file` with `application/x-gzip` content type which is an archive containing a Helm chart.

Request body example:

	Content-Type: multipart/form-data; boundary=----boundary 	----boundary 	Content-Disposition: form-data; name="file"; filename="my-workload-1.0.1.tgz" 	Content-Type: application/x-gzip 	[TGZ_DATA] 	----boundary

## Path parameters

- `orgId` string, required

## Response `201`

The newly created Workload Profile Chart Version metadata.

- WorkloadProfileChartVersionResponse — Each Workload Profile Chart has one or more Versions associated with it.
  - `created_at` string, date-time, required — Creation date
  - `created_by` string, required — User created the profile
  - `org_id` string, required — Organization ID
  - `id` string, required — Workload Profile Chart Version ID
  - `version` string, required — Version

## Other responses

- `400` — The request was invalid. More detail can be found in the error body.
- `409` — The request itself is valid however it could not be applied based on the current state of the resource. More detail can be found in the error body.

---

[API](https://skmtc.net/humanitec/apis/humanitec-api.md) · [All operations](https://skmtc.net/humanitec/apis/humanitec-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/humanitec/humanitec-api/revisions/e21ad140ec3c/schema)