---
title: "Put Package"
slug: "compute-cloudfunctions-putpackage"
updated: 2026-09-17T10:05:57Z
published: 2026-09-17T10:05:57Z
canonical: "api.ncloud-docs.com/compute-cloudfunctions-putpackage"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://api.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Put Package

Available in Classic and VPC

Create or edit a Cloud Functions package.

## Request

This section describes the request format. The method and URI are as follows:

| Method | URI |
| --- | --- |
| PUT | /api/v2/packages/{packageName} |

              Note

              

Singapore and Japan Regions are available only in the VPC environment.

### Request headers

For information about the headers common to all Cloud Functions APIs, see [Cloud Functions request headers](/docs/en/compute-cloudfunctions#%EC%9A%94%EC%B2%AD%ED%97%A4%EB%8D%94).

### Request path parameters

You can use the following path parameters with your request:

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `packageName` | String | Required | Package name - Enter 1-50 characters, including English letters, numbers, and special characters "-" and "_". - It can't start with "-". |

### Request query parameters

You can use the following query parameters with your request:

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `platform` | String | Optional | Platform type - `vpc` \| `classic` (default) |

### Request body

You can include the following data in the body of your request: If there are no fields in the request body, it should be requested as `{}` empty JSON object.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `description` | String | Optional | Package description (byte) - 0-3000 |
| `parameters` | Object | Optional | Default parameters of the package - JSON in the form of `{"key": "value"}` - Priority of applying parameters when running actions - 1st priority: Runtime parameters passed at runtime - 2nd priority: Default parameters of connected triggers - 3rd priority: Default parameters in actions - 4th priority: Default parameters of included packages |

### Request example

The request example is as follows:

```
curl --location --request PUT 'https://cloudfunctions.apigw.ntruss.com/api/v2/packages/package003?platform=classic' \
--header 'Content-Type: application/json' \
--header 'x-ncp-apigw-timestamp: {Timestamp}' \
--header 'x-ncp-iam-access-key: {Sub Account Access Key}' \
--header 'x-ncp-apigw-signature-v2: {API Gateway Signature} \
--data '{
    "description": "Create package",
    "parameters": {
        "name": "package003",
    }
}'
```

## Response

This section describes the response format.

### Response body

The response body includes the following data:

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `content` | String | - | Package creation and modification information |
| `content.description` | String | - | Package description |
| `content.name` | String | - | Package name |
| `content.namespace` | String | - | Namespace of the user |
| `content.parameters` | Object | - | Default parameters of the package |
| `content.resourceId` | String | - | Package's resource ID |

### Response status codes

For information about the HTTP status codes common to NAVER Cloud Platform, see [Ncloud API response status codes](/docs/en/common-ncpapi#3%EC%9D%91%EB%8B%B5%EC%83%81%ED%83%9C%EC%BD%94%EB%93%9C).

### Response example

The response example is as follows:

```
{
    "content": {
        "description": "put package",
        "name": "package003",
        "namespace": "****YBN*****",
        "parameters": {
            "name": "package003"
        },
        "resourceId": "xn***"
    }
}
```