Skip to main content
The verial datasets commands manage 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.

Subcommands

verial datasets list

List datasets visible to your organization. Synopsis:
Example:
REST equivalent: GET /datasets.

verial datasets create

Create a typed dataset. The --type value determines how contents are stored and which simulators can consume it. Synopsis:
Options: Example:
REST equivalent: POST /datasets.

verial datasets get

Fetch a single dataset, including its config and (where applicable) file manifest. Synopsis:
Example:
REST equivalent: GET /datasets/:id.

verial datasets update

Rename or redescribe a dataset. Contents are mutated through type-specific endpoints, not this command. Synopsis:
Example:
REST equivalent: PATCH /datasets/:id.

verial datasets delete

Delete a dataset. Sandboxes that branched from it retain their child datasets. Synopsis:
REST equivalent: DELETE /datasets/:id.

Next Steps

Datasets

Dataset types, config shape, and sandbox branching.

Datasets API

Full REST parameters and response schema.