> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/server-side/command-line-interface/ab-tasty-cli-reference-v1xx/feature-experimentation/feature-experimentation-variation.md).

# variation

## abtasty-cli feature-experimentation variation create

#### NAME

`abtasty-cli feature-experimentation variation create` - Create a variation

#### SYNOPSIS

`abtasty-cli feature-experimentation variation create [--campaign-id = CAMPAIGN_ID] [--variation-group-id = VARIATION_GROUP_ID] [-d DATA_RAW | --data-raw = DATA_RAW]`

#### DESCRIPTION

Create a variation in your variation group

#### EXAMPLES

```shell
abtasty-cli feature-experimentation variation create --campaign-id CAMPAIGN_ID --variation-group-id VARIATION_GROUP_ID -d DATA_RAW
```

```shell
abtasty-cli feature-experimentation variation create --campaign-id CAMPAIGN_ID --variation-group-id VARIATION_GROUP_ID -d "{\"name\":\"Variation 1\",\"reference\":false,\"allocation\":95,\"modifications\":{\"type\":\"FLAG\",\"value\":{\"myColor\":\"blue\"}}}"
```

#### REQUIRED FLAGS

`--campaign-id = _CAMPAIGN_ID_`

The campaign id of your variation

`--variation-group-id = _VARIATION_GROUP_ID_`

the variation group id of your variation

`--data-raw = _DATA_RAW_`

The raw data contains all the info to create your variation, check the [Remote Control API documentation](https://docs.developers.flagship.io/reference/schema-variations) for more details.

{% hint style="danger" %}
❗️ Raw data format

Note that you should insert data without spaces, line breaks, tabulation etc...
{% endhint %}

***

## abtasty-cli feature-experimentation variation list

#### NAME

`abtasty-cli feature-experimentation variation list` - List all variations

#### SYNOPSIS

`abtasty-cli feature-experimentation variation list [--campaign-id = CAMPAIGN_ID] [--variation-group-id = VARIATION_GROUP_ID] \[--output-format = OUTPUT_FORMAT [table|json|json-pretty]]`

#### DESCRIPTION

List all variations in your variation group

#### EXAMPLES

```shell
abtasty-cli feature-experimentation variation list --campaign-id CAMPAIGN_ID --variation-group-id VARIATION_GROUP_ID
```

#### REQUIRED FLAGS

`--campaign-id = _CAMPAIGN_ID_`

The campaign id of your variation

`--variation-group-id = _VARIATION_GROUP_ID_`

the variation group id of your variation

#### FLAGS

`--output-format = _OUTPUT_FORMAT_`

The output format for printing command output resources. The default is table. The supported formats are: json-pretty, table, json.

***

## flagship variation get

#### NAME

`abtasty-cli feature-experimentation variation get` - Get a variation

#### SYNOPSIS

`abtasty-cli feature-experimentation variation get [--campaign-id = CAMPAIGN_ID] [--variation-group-id = VARIATION_GROUP_ID] [-i VARIATION_ID | --id = VARIATION_ID]`

#### DESCRIPTION

Get a variation in your variation group

#### EXAMPLES

```shell
abtasty-cli feature-experimentation variation get --campaign-id CAMPAIGN_ID --variation-group-id VARIATION_GROUP_ID -i VARIATION_ID
```

#### REQUIRED FLAGS

`--campaign-id = _CAMPAIGN_ID_`

The campaign id of your variation

`--variation-group-id = _VARIATION_GROUP_ID_`

the variation group id of your variation

\`--id = *VARIATION\_ID*

The id of the variation you want to display

#### FLAGS

`--output-format _OUTPUT_FORMAT_`

The output format for printing command output resources. The default is table. The supported formats are: json-pretty, table, json.

***

## abtasty-cli feature-experimentation variation edit

#### NAME

`abtasty-cli feature-experimentation variation edit` - Edit a variation

#### SYNOPSIS

`abtasty-cli feature-experimentation variation edit [--campaign-id = CAMPAIGN_ID] [--variation-group-id = VARIATION_GROUP_ID] [-i VARIATION_ID | --id = VARIATION_ID] [-d DATA_RAW | --data-raw = DATA_RAW]`

#### DESCRIPTION

Edit a variation in your variation group

#### EXAMPLES

```shell
abtasty-cli feature-experimentation variation edit --campaign-id CAMPAIGN_ID --variation-group-id VARIATION_GROUP_ID -i VARIATION_ID -d DATA_RAW
```

#### REQUIRED FLAGS

`--campaign-id = _CAMPAIGN_ID_`

The campaign id of your variation

`--variation-group-id = _VARIATION_GROUP_ID_`

the variation group id of your variation

`--id = _VARIATION_ID_`

The id of the variation you want to edit

`--data-raw = _DATA_RAW_`

The raw data contains all the info to edit your variation, check the [Remote Control API documentation](https://docs.developers.flagship.io/reference/schema-variations) for details

{% hint style="danger" %}
❗️ Raw data format

Note that you should insert data without spaces, line breaks, tabulation etc...
{% endhint %}

***

## abtasty-cli feature-experimentation variation delete

#### NAME

`abtasty-cli feature-experimentation variation delete` - Delete a variation

#### SYNOPSIS

`abtasty-cli feature-experimentation variation-group delete [--campaign-id = CAMPAIGN_ID] [--variation-group-id = VARIATION_GROUP_ID] [-i VARIATION_ID | --id = VARIATION_ID]`

#### DESCRIPTION

Delete a variation in your variation group

#### EXAMPLES

```shell
abtasty-cli feature-experimentation variation delete --campaign-id CAMPAIGN_ID --variation-group-id VARIATION_GROUP_ID -i VARIATION_ID
```

#### REQUIRED FLAGS

`--campaign-id = _CAMPAIGN_ID_`

The campaign id of your variation

`--variation-group-id = _VARIATION_GROUP_ID_`

the variation group id of your variation

`--id = _VARIATION_ID_`

The id of the variation you want to delete


---

# 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://docs.abtasty.com/server-side/command-line-interface/ab-tasty-cli-reference-v1xx/feature-experimentation/feature-experimentation-variation.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.
