<a id="cli-aws-partnercentral-marketing-batch-create-campaign-asset"></a>

# batch-create-campaign-asset

## Description

Instantiates one or more of the campaign template’s blueprints as assets of this campaign.

The only asset-create operation: DG-038 deleted the singular CreateCampaignAsset, and AWS Batch Operations makes exposing a singular alongside a batch optional (“which MAY actually be exposed in addition”). It also replaced kit instantiation – CreateCampaign creates zero assets, so this is the only path by which an asset comes into existence.

Errors here are whole-request only, and nothing is written when one is thrown. Per-entry failures ride in the response’s `Errors` list with a 200. ServiceQuotaExceededException is deliberately absent: a campaign holds at most one asset per blueprint (I-15), so the ceiling is the size of the bound kit and a request of unique valid entries cannot exceed it.

See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/partnercentral-marketing-2026-05-31/BatchCreateCampaignAsset)

## Synopsis

```
  batch-create-campaign-asset
--catalog <value>
--campaign-identifier <value>
--entries <value>
[--cli-input-json | --cli-input-yaml]
[--generate-cli-skeleton <value>]
[--debug]
[--endpoint-url <value>]
[--no-verify-ssl]
[--no-paginate]
[--output <value>]
[--query <value>]
[--profile <value>]
[--region <value>]
[--version <value>]
[--color <value>]
[--no-sign-request]
[--ca-bundle <value>]
[--cli-read-timeout <value>]
[--cli-connect-timeout <value>]
[--cli-binary-format <value>]
[--no-cli-pager]
[--cli-auto-prompt]
[--no-cli-auto-prompt]
[--cli-error-format <value>]
[--help]
```

## Options

`--catalog` (string) [required]

> The catalog (AWS or Sandbox).

> Possible values:

> * `AWS`
> * `Sandbox`

`--campaign-identifier` (string) [required]

> The campaign identifier.

> Constraints:

> * min: `18`
> * max: `200`
> * pattern: `(arn:[a-z-]+:partnercentral:[a-z0-9-]+:[0-9]{12}:catalog/[A-Za-z]+/campaign/)?camp-[A-Za-z0-9]{13}`

`--entries` (list) [required]

> The blueprints to instantiate, one entry each.

> Constraints:

> * min: `1`
> * max: `25`

> (structure)

> > One blueprint to instantiate.

> > Carries nothing but the blueprint’s identity, and that is the point rather than a saving: category, name, FileFormat and platform are all derived from the named blueprint, so no caller has a member with which to contradict the pinned schema (asset design section 3.1).

> > There is deliberately no per-entry ClientToken. AWS Batch Operations requires a request identifierper entry – “a request identifier CAN either be a resource identifier or a client idempotency token” – and SourceAssetTemplateIdentifier is a resource identifier, unique across entries and echoed in this entry’s error. Idempotency is structural rather than token-based: an asset id is derived from (CampaignId, SourceAssetTemplateId), so a replayed entry resolves to the same asset (I-16).

> > SourceAssetTemplateIdentifier -> (string) [required]

> > > The asset template to instantiate, as returned by GetCampaignTemplate in CampaignTemplate.AssetTemplates[].id.

> > > Must belong to the campaign’s own campaign template. An asset’s editable field schema is copied from this blueprint at creation and pinned, so an asset without one could be neither validated on update nor made live.

> > > Also this entry’s request identifier: it MUST be unique across the request’s entries, since a campaign holds at most one asset per blueprint (I-15) and two entries naming the same blueprint could not both succeed.

> > > Constraints:

> > > * min: `1`
> > > * max: `2048`
> > > * pattern: `[\w:/+=,.@-]+`

Shorthand Syntax:

```
SourceAssetTemplateIdentifier=string ...
```

JSON Syntax:

```json
[
  {
    "SourceAssetTemplateIdentifier": "string"
  }
  ...
]
```

`--cli-input-json` | `--cli-input-yaml` (string)
Reads arguments from the JSON string provided. The JSON string follows the format provided by `--generate-cli-skeleton`. If other arguments are provided on the command line, those values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. This may not be specified along with `--cli-input-yaml`.

`--generate-cli-skeleton` (string)
Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value `input`, prints a sample input JSON that can be used as an argument for `--cli-input-json`. Similarly, if provided `yaml-input` it will print a sample input YAML that can be used with `--cli-input-yaml`. If provided with the value `output`, it validates the command inputs and returns a sample output JSON for that command. The generated JSON skeleton is not stable between versions of the AWS CLI and there are no backwards compatibility guarantees in the JSON skeleton generated.

## Global Options

`--debug` (boolean)

Turn on debug logging.

`--endpoint-url` (string)

Override command’s default URL with the given URL.

`--no-verify-ssl` (boolean)

By default, the AWS CLI uses SSL when communicating with AWS services. For each SSL connection, the AWS CLI will verify SSL certificates. This option overrides the default behavior of verifying SSL certificates.

`--no-paginate` (boolean)

Disable automatic pagination. If automatic pagination is disabled, the AWS CLI will only make one call, for the first page of results.

`--output` (string)

The formatting style for command output.

* json
* text
* table
* yaml
* yaml-stream
* off

`--query` (string)

A JMESPath query to use in filtering the response data.

`--profile` (string)

Use a specific profile from your credential file.

`--region` (string)

The region to use. Overrides config/env settings.

`--version` (string)

Display the version of this tool.

`--color` (string)

Turn on/off color output.

* on
* off
* auto

`--no-sign-request` (boolean)

Do not sign requests. Credentials will not be loaded if this argument is provided.

`--ca-bundle` (string)

The CA certificate bundle to use when verifying SSL certificates. Overrides config/env settings.

`--cli-read-timeout` (int)

The maximum socket read time in seconds. If the value is set to 0, the socket read will be blocking and not timeout. The default value is 60 seconds.

`--cli-connect-timeout` (int)

The maximum socket connect time in seconds. If the value is set to 0, the socket connect will be blocking and not timeout. The default value is 60 seconds.

`--cli-binary-format` (string)

The formatting style to be used for binary blobs. The default format is base64. The base64 format expects binary blobs to be provided as a base64 encoded string. The raw-in-base64-out format preserves compatibility with AWS CLI V1 behavior and binary values must be passed literally. When providing contents from a file that map to a binary blob `fileb://` will always be treated as binary and use the file contents directly regardless of the `cli-binary-format` setting. When using `file://` the file contents will need to properly formatted for the configured `cli-binary-format`.

* base64
* raw-in-base64-out

`--no-cli-pager` (boolean)

Disable cli pager for output.

`--cli-auto-prompt` (boolean)

Automatically prompt for CLI input parameters.

`--no-cli-auto-prompt` (boolean)

Disable automatically prompt for CLI input parameters.

`--cli-error-format` (string)

The formatting style for error output. By default, errors are displayed in enhanced format.

* legacy
* json
* yaml
* text
* table
* enhanced

`--help` (boolean)

Display help for the command/subcommand.

## Output

Errors -> (list)

> One entry per blueprint that could not be instantiated. Empty, never absent, when all entries succeeded.

> Constraints:

> * min: `0`
> * max: `25`

> (structure)

> > Why one entry could not be instantiated.

> > SourceAssetTemplateId -> (string) [required]

> > > The failing entry’s request identifier, so a caller can match this error to the entry it sent.

> > > Constraints:

> > > * min: `1`
> > > * max: `2048`
> > > * pattern: `[\w:/+=,.@-]+`

> > Code -> (string) [required]

> > > Error code – ResourceNotFoundException when the blueprint is not on the campaign’s bound template, InternalServerException otherwise. Throttling never appears here: DG throttles per operation, so a throttle fails the whole batch.

> > Message -> (string) [required]

> > > Human-readable cause.

Successful -> (list)

> One entry per asset that exists as a result of this call, whether created here or already present.

> Constraints:

> * min: `0`
> * max: `25`

> (structure)

> > One asset that exists as a result of this call.

> > SourceAssetTemplateId -> (string) [required]

> > > The entry’s request identifier.

> > > Constraints:

> > > * min: `1`
> > > * max: `2048`
> > > * pattern: `[\w:/+=,.@-]+`

> > Id -> (string) [required]

> > > The asset’s identifier, derived from (CampaignId, SourceAssetTemplateId) rather than minted, so the same entry always resolves to the same id.

> > > Constraints:

> > > * min: `17`
> > > * max: `17`
> > > * pattern: `ast-[0-9a-z]{13}`

> > Layout -> (structure)

> > > For a multi-layout blueprint, the asset’s layout options, so a client can render the first layout picker without reading each asset back. Nothing is selected at creation. Absent for a single-layout blueprint.

> > > Selected -> (string)

> > > > The selected option’s value. An asset is created with its first option selected; an asset created before that rule, with none stored, reports and activates its first option.

> > > > Constraints:

> > > > * min: `1`
> > > > * max: `64`
> > > > * pattern: `[A-Za-z][A-Za-z0-9_]*`

> > > Options -> (list) [required]

> > > > Every option the asset was created with, in authored order.

> > > > Constraints:

> > > > * min: `0`
> > > > * max: `10`

> > > > (structure)

> > > > > One layout a multi-layout asset offers.

> > > > > Value -> (string) [required]

> > > > > > The value that selects this option.

> > > > > > Constraints:

> > > > > > * min: `1`
> > > > > > * max: `64`
> > > > > > * pattern: `[A-Za-z][A-Za-z0-9_]*`

> > > > > Label -> (string)

> > > > > > Display label.

> > > > > > Constraints:

> > > > > > * min: `1`
> > > > > > * max: `200`

> > > > > FieldIds -> (list) [required]

> > > > > > The fields this option uses: the FieldValues that stay in scope when it is selected. Lets a client show an option’s form before selecting it.

> > > > > > Constraints:

> > > > > > * min: `0`
> > > > > > * max: `150`

> > > > > > (string)

> > > > > > > A field’s slot name — the developer-readable key that matches a {{fieldId}} placeholder in the layout skeleton (e.g. “Headline”, “CtaUrl”), or the form field name in a document template (e.g. “Page 2 Title”). Platform-assigned and semantic (not a service-generated opaque Id), so it has its own constrained shape rather than reusing Id.

> > > > > > > Single spaces between words are allowed because document templates name their fields that way, and this shape is the input type for editing them. Leading, trailing and repeated spaces are not, so that “Title” and “Title “ cannot be two different fields.

> > > > > > > Constraints:

> > > > > > > * min: `1`
> > > > > > > * max: `64`
> > > > > > > * pattern: `[A-Za-z][A-Za-z0-9_]*( [A-Za-z0-9_]+)*`

> > > > > LayoutPreviews -> (list)

> > > > > > This option’s pages, in page order.

> > > > > > Constraints:

> > > > > > * min: `0`
> > > > > > * max: `20`

> > > > > > (structure)

> > > > > > > A rendering of an AWS-authored layout skeleton or placeholder image.

> > > > > > > The url is a stable, cache-friendly CloudFront URL rather than a presigned GET, because the bytes are AWS marketing content that is already public. The key’s random segment is the object’s only protection, so the URL is a bearer credential for the object and is withheld entirely while a template is not yet effective — see CampaignTemplate.EffectiveDateBegin.

> > > > > > > Format -> (string) [required]

> > > > > > > > The format of the referenced object.

> > > > > > > > Possible values:

> > > > > > > > * `HTML`
> > > > > > > > * `PDF`
> > > > > > > > * `IMAGE`

> > > > > > > Url -> (string) [required]

> > > > > > > > A stable URL serving the object. Not presigned, so it does not expire.

> > > > > > > > Constraints:

> > > > > > > > * min: `1`
> > > > > > > > * max: `2048`

> > > > > > > PageType -> (string)

> > > > > > > > Which page of a multi-page layout this is. Present only for LANDING_PAGE, which genuinely has two layout objects — the page carrying the form, and the confirmation page shown after submit — and absent for every other category, which has one.

> > > > > > > > A confirmation page is a second LAYOUT, never a second asset: modelling it as its own asset would give it a lifecycle, an activation and a state it does not have.

> > > > > > > > Possible values:

> > > > > > > > * `FORM`
> > > > > > > > * `CONFIRMATION`
