> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/3.7.0/developer-tools-and-resources/api-reference/dry-run-mode-using-apis/creating-virtual-account-v2.md).

# Creating Virtual Account (Api-Version: 2)

**`POST /policies/{policyId}/dry-run/user`** — requires `Api-Version: 2` header

Creates a new virtual user for the selected dry-run policy and **returns the created user object**. Only users with the Standard Registry role are allowed to make the request.

Version 2 differs from V1 in that it returns the created virtual user object and optionally accepts `savepointIds` in the request body to scope creation to a specific savepoint context.

**Authentication:** Bearer token required (`Authorization: Bearer <token>`)

**Permission:** `Permissions.POLICIES_POLICY_UPDATE`

***

## Request

### Headers

| Header        | Value | Required | Description                                                               |
| ------------- | ----- | -------- | ------------------------------------------------------------------------- |
| `Api-Version` | `2`   | Yes      | Enables V2 behaviour (returns created user object, supports savepointIds) |

### Path Parameters

| Parameter  | Type   | Required | Description |
| ---------- | ------ | -------- | ----------- |
| `policyId` | String | Yes      | Policy ID   |

### Request Body

Optional. Provide `savepointIds` to scope the virtual user creation to a specific savepoint context.

```json
{
  "savepointIds": [
    "67c85d2fcebecbe1c0231522",
    "67c85d35cebecbe1c0231523"
  ]
}
```

| Field          | Type      | Required | Description                                          |
| -------------- | --------- | -------- | ---------------------------------------------------- |
| `savepointIds` | String\[] | No       | Array of savepoint IDs to scope the creation context |

***

## Response

### Success Response

**Status:** `201 Created`

Returns the created virtual user object.

```json
{
  "username": "Virtual User 3",
  "did": "did:hedera:testnet:zHcDLGFNymFAJiMBKnpbHDgjvTn6yZnwkPPeFhtJBECH_0.0.4532001",
  "hederaAccountId": "0.0.1774730865730",
  "active": false
}
```

| Field             | Type    | Description                                    |
| ----------------- | ------- | ---------------------------------------------- |
| `username`        | string  | Generated username for the virtual user        |
| `did`             | string  | DID of the virtual user                        |
| `hederaAccountId` | string  | Hedera account ID assigned to the virtual user |
| `active`          | boolean | Whether the virtual user is currently active   |

### Error Responses

| Status                      | Description               |
| --------------------------- | ------------------------- |
| `401 Unauthorized`          | Missing or invalid token  |
| `403 Forbidden`             | Insufficient permissions  |
| `500 Internal Server Error` | Unexpected server failure |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guardian.hedera.com/docs/3.7.0/developer-tools-and-resources/api-reference/dry-run-mode-using-apis/creating-virtual-account-v2.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
