---
title: "PostAccount"
slug: "storage-archivestorage-postaccount"
tags: ["Archive Storage"]
updated: 2026-09-17T10:12:27Z
published: 2026-09-17T10:12:27Z
canonical: "api.ncloud-docs.com/storage-archivestorage-postaccount"
---

> ## 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.

# PostAccount

Available in Classic and VPC

Set or change metadata for an account.

## Requests

The following describes the request format for the endpoint. The request format is as follows.

| Method | URI |
| --- | --- |
| POST | /v1/AUTH_{project_id} |

### Request headers

The following describes headers.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `X-Auth-Token` | String | Required | Value of the issued token |
| `X-Account-Meta-Temp-URL-Key` | String | Optional | Secret key value for the temporary URL |
| `X-Account-Meta-Temp-URL-Key-2` | String | Optional | Second secret key value for the temporary URL |
| `X-Account-Meta-name` | String | Optional | Set metadata for the account - The `name` part of the header name acts as a key for metadata |
| `X-Remove-Account-name` | String | Optional | Delete metadata from the account - The `name` part of the header name acts as a key for metadata |

              Note

              

You can request deletion by entering an empty value in the metadata `X-Account-Meta-name` header, but some tools may not allow you to enter an empty value in the header. In this case, make the request with `X-Remove-Account-Meta-name`.

The result of the request based on the request header settings is as follows.

| Request headers | Result |
| --- | --- |
| If the request header contains no values in the account metadata, only a key, and the key already exists in the account | The API deletes the applicable metadata item |
| If the request header contains no value of account metadata, only a key, and the key does not exist in the account. | The API ignores the applicable metadata key |
| If both the key and value of the account metadata are present in the request header, and the key already exists in the account | The API updates the applicable metadata |
| If both the key and value of the account metadata are present in the request header, and the key does not exist in the account | The API adds the applicable metadata |
| If the request header omits account metadata, and the account already has the metadata | The API doesn't change metadata that already exists |

              Note

              

- Metadata keys are not case sensitive and can be composed of any ASCII 7-bit character. However, this excludes ASCII characters 0 - 31, the DEL character, etc.
- Metadata values must be UTF-8 encoded and then URL encoded. This is the default rule for HTTP/1.1.

### Request path parameters

The following describes the request path parameters.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `project_id` | String | Required | Project ID - For more information on how to check the project ID, see [Archive Storage overview](/docs/en/storage-archivestorage#%EC%9D%B8%EC%A6%9D) |

### Request example

The following is a sample request.

#### Request metadata creation

The following is a sample request of creating metadata.

```
curl -X POST "https://kr.archive.ncloudstorage.com/v1/AUTH_{project_id}" 
-H "X-Auth-Token: $token"
-H "X-Account-Meta-{name}: $account-metadata-string"
```

#### Request metadata modification

The following is a sample request of editing metadata.

```
curl -X POST "https://kr.archive.ncloudstorage.com/v1/AUTH_{project_id}" 
-H "X-Auth-Token: $token"
-H "X-Account-Meta-{name}: $account-metadata-string"
```

#### Request metadata deletion

The following is a sample request of deleting metadata.

```
curl -X POST "https://kr.archive.ncloudstorage.com/v1/AUTH_{project_id}" 
-H "X-Auth-Token: $token"
-H "X-Remove-Account-Meta-{name}: $account-metadata-string"
```

## Responses

The following describes the response format.

### Response headers

For response headers common to all Archive Storage APIs, see [Archive Storage common response headers](/docs/en/storage-archivestorage#%EC%9D%91%EB%8B%B5%ED%97%A4%EB%8D%94).

### Response example

The following is a sample response.

#### Response when requesting creation of metadata

The following is a sample response when requesting to create metadata.

```
HTTP/1.1 204 No Content
Content-Type: text/html; charset=UTF-8
Content-Length: 0
X-Trans-Id: txad3702ae436640d1a9897-005b975c51
X-Openstack-Request-Id: txad3702ae436640d1a9897-005b975c51
Date: Tue, 11 Sep 2018 06:10:25 GMT
```

#### Response when requesting modification of metadata

The following is a sample response when requesting to edit metadata.

```
HTTP/1.1 204 No Content
Content-Length: 0
Content-Type: text/html; charset=UTF-8
X-Trans-Id: txc5a65e1d20074023912c6-005b975c97
X-Openstack-Request-Id: txc5a65e1d20074023912c6-005b975c97
Date: Tue, 11 Sep 2018 06:11:35 GMT
```

#### Response when requesting deletion of metadata

The following is a sample response when requesting to delete metadata.

```
HTTP/1.1 204 No Content
Content-Length: 0
Content-Type: text/html; charset=UTF-8
X-Trans-Id: txf2874df785bd470eaf3b8-005b975d40
X-Openstack-Request-Id: txf2874df785bd470eaf3b8-005b975d40
Date: Tue, 11 Sep 2018 06:14:24 GMT
```