# Create dictionary (create)

Create a new dictionary.

### Parameters

These parameters work with any `cmd`.

| Name           | Type    | Required   | Description                                                                                                                                                                        |
| -------------- | ------- | ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `serviceid`    | string  | Cloud only | Cloud API key. Required for Cloud requests. Not used on-premises.                                                                                                                  |
| `format`       | string  | No         | Response format. Values: `json` (default), `xml`.                                                                                                                                  |
| `callback`     | string  | No         | JSONP wrapper function name. Use only with `format=json`.                                                                                                                          |
| `short_answer` | boolean | No         | <p>JSON only. When <code>true</code>, shortens JSON keys to reduce payload size.<br>See <a href="/pages/VXTsQ0sY5BFRLUsqxnbL#boolean-parameter-values">boolean parameters</a>.</p> |

See [Overview](/v6.12.0/api-reference/overview.md#common-parameters) for details.

#### Command specific parameters

| Parameter  | Type   | Required | Default           | Notes                                   |
| ---------- | ------ | -------- | ----------------- | --------------------------------------- |
| `cmd`      | string | Yes      | `user_dictionary` | Command name.                           |
| `action`   | string | Yes      | `create`          | Action name.                            |
| `name`     | string | Yes      |                   | Dictionary name to create.              |
| `wordlist` | string | No       |                   | Optional comma-separated initial words. |

### Behavior

* Creates a new dictionary.
* Adds `wordlist` words if provided.

{% hint style="warning" %}
`create` fails if the dictionary already exists.

Use [addword(s)](/v6.12.0/api-reference/user-custom-dictionary-api/actions/add-word-s-addword-addwords.md) if you want auto-create behavior.
{% endhint %}

### Response

Returns the created dictionary state.

See [Response format](/v6.12.0/api-reference/user-custom-dictionary-api/response-format.md).

### Errors

Common errors:

* Dictionary already exists.
* Dictionary name is missing, invalid, or longer than 50 characters.
* If `wordlist` is present:
  * a word is empty
  * a word contains forbidden symbols
  * a word is longer than 63 characters

See [Errors reference](/v6.12.0/api-reference/user-custom-dictionary-api/errors-reference.md).

### Examples

<details>

<summary>Create an empty dictionary</summary>

**Request body (JSON):**

```json
{
  "cmd": "user_dictionary",
  "action": "create",
  "name": "my_dict"
}
```

**Response (JSON):**

```json
{
  "name": "my_dict",
  "action": "create",
  "wordlist": [],
  "modificationTime": 1772124021
}
```

</details>

<details>

<summary>Create a dictionary with initial words</summary>

**Request body (JSON):**

```json
{
  "cmd": "user_dictionary",
  "action": "create",
  "name": "my_dict",
  "wordlist": "API,SDK"
}
```

**Response (JSON):**

```json
{
  "name": "my_dict",
  "action": "create",
  "wordlist": ["API", "SDK"],
  "modificationTime": 1772124021
}
```

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.wproofreader.com/v6.12.0/api-reference/user-custom-dictionary-api/actions/create-dictionary-create.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.