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

# verial datasets

> Manage datasets that back simulators in your environments.

The `verial datasets` commands manage [Datasets](/api-reference/resources/datasets) — typed data containers (FHIR bundles, file manifests, SFTP drops, HL7 messages) that back simulators. Use them to script dataset lifecycle in CI or before attaching data to an environment.

Authentication is required. See [verial auth](/cli/auth).

## Subcommands

| Command                  | Description                             |
| ------------------------ | --------------------------------------- |
| `verial datasets list`   | List datasets in your organization.     |
| `verial datasets create` | Create a dataset of a given type.       |
| `verial datasets get`    | Get a single dataset by ID.             |
| `verial datasets update` | Update a dataset's name or description. |
| `verial datasets delete` | Delete a dataset.                       |

## verial datasets list

List datasets visible to your organization.

Synopsis:

```bash theme={null}
verial datasets list
```

Example:

```bash theme={null}
verial datasets list
```

```
ID                  NAME                     TYPE     CREATED
ds_clxyz001         Primary Care FHIR        FHIR     4/10/2026, 9:02:11 AM
ds_clxyz002         Referral Fax Files       Files    4/12/2026, 11:47:30 AM
```

REST equivalent: [GET /datasets](/api-reference/datasets/list).

## verial datasets create

Create a typed dataset. The `--type` value determines how contents are stored and which simulators can consume it.

Synopsis:

```bash theme={null}
verial datasets create --name <name> --type <type> [--description <desc>]
```

Options:

| Flag                   | Description                            | Required |
| ---------------------- | -------------------------------------- | -------- |
| `--name <name>`        | Dataset name.                          | Yes      |
| `--type <type>`        | One of `FHIR`, `Files`, `Sftp`, `HL7`. | Yes      |
| `--description <desc>` | Free-text description.                 | No       |

Example:

```bash theme={null}
verial datasets create \
  --name "Primary Care FHIR" \
  --type FHIR \
  --description "Seed bundle for primary care scenarios"
```

REST equivalent: [POST /datasets](/api-reference/datasets/create).

## verial datasets get

Fetch a single dataset, including its config and (where applicable) file manifest.

Synopsis:

```bash theme={null}
verial datasets get --id <id>
```

Example:

```bash theme={null}
verial datasets get --id ds_clxyz001
```

REST equivalent: [GET /datasets/:id](/api-reference/datasets/get).

## verial datasets update

Rename or redescribe a dataset. Contents are mutated through type-specific endpoints, not this command.

Synopsis:

```bash theme={null}
verial datasets update --id <id> [--name <name>] [--description <desc>]
```

Example:

```bash theme={null}
verial datasets update --id ds_clxyz001 --name "Primary Care FHIR (v2)"
```

REST equivalent: [PATCH /datasets/:id](/api-reference/datasets/update).

## verial datasets delete

Delete a dataset. Sandboxes that branched from it retain their child datasets.

Synopsis:

```bash theme={null}
verial datasets delete --id <id>
```

```
Deleted ds_clxyz001
```

REST equivalent: [DELETE /datasets/:id](/api-reference/datasets/delete).

## Next Steps

<CardGroup cols={2}>
  <Card title="Datasets" icon="database" href="/api-reference/resources/datasets">
    Dataset types, config shape, and sandbox branching.
  </Card>

  <Card title="Datasets API" icon="code" href="/api-reference/datasets/list">
    Full REST parameters and response schema.
  </Card>
</CardGroup>