---
title: "Attach an asset to an ad"
method: POST
path: "/api/v1/ad-assets"
tags: ["ad-assets"]
---

# Attach an asset to an ad

`POST /api/v1/ad-assets`

## Request

- Base URL: `https://api.growomat.com`
- URL: `https://api.growomat.com/api/v1/ad-assets`
- Auth: HTTP bearer

Attaches an asset to an ad (`scope: AD`) or to an ad group (`scope: AD_GROUP`) in a role such as `MARKETING_IMAGE` or `VIDEO`. Changes reach the ad platforms on the next sync.

**Errors**

- `400 VALIDATION_ERROR`: the body failed validation; `details.issues[]` names each field.

## Headers

- `X-Space-Id` string

## Request body

- AdAssetCreate: Attach an asset to an ad (`scope: AD`, `adId` required) or to an ad group (`scope: AD_GROUP`, `adGroupId` required).
  - `scope` 'AD' | 'AD_GROUP', required: Whether the asset attaches to one ad or to the whole ad group.
  - `adId` string: The ad. Required when `scope` is `AD`.
  - `adGroupId` string: The ad group. Required when `scope` is `AD_GROUP`.
  - `campaignId` string: The campaign. Optional; derived from the ad or ad group when omitted.
  - `assetId` string, required: The asset.
  - `role` 'MARKETING_IMAGE' | 'SQUARE_MARKETING_IMAGE' | 'PORTRAIT_MARKETING_IMAGE' | 'LOGO' | 'LANDSCAPE_LOGO' | 'YOUTUBE_VIDEO' | 'VIDEO', required: What the asset is used as.

## Response `200`

OK. The result is in `data`. List responses also carry `meta` with `nextCursor` and `total`.

- SuccessEnvelope: The shape of every successful response.
  - `data` unknown, required
  - `meta` object: Present on list responses.
    - `nextCursor` union: Pass as `cursor` to get the next page. `null` on the last page.
      - string
      - number
    - `total` integer: Number of items in this page.

## Other responses

- `201`: Created. The new resource is in `data`.
- `400`: The request is malformed or fails validation. `error.code` is `VALIDATION_ERROR` (with `details.issues[]` naming each field), `INVALID_REQUEST` (the body is not valid JSON or has the wrong shape), or one of the specific codes listed in this operation's description.
- `401`: The bearer token is missing, invalid, expired or revoked (`INVALID_TOKEN`).
- `403`: The token lacks the scope this operation needs (`INSUFFICIENT_SCOPE`), the plan is read-only (`READ_ONLY_MODE`), or the caller is not a member of the Space named in `X-Space-Id` (`NOT_A_MEMBER`).
- `404`: No such resource in the active Space (`NOT_FOUND`), or `X-Space-Id` names a Space that does not exist (`SPACE_NOT_FOUND`).
- `409`: The request conflicts with the current state, for example a delete blocked by dependents or a sync already running. This operation's description names the `error.code` values it can return.
- `429`: Too many requests (`RATE_LIMITED`). Wait for the number of seconds in the `Retry-After` header, then retry.

---

[API](https://skmtc.dev/growomat/apis/growomat-public-api.md) · [All operations](https://skmtc.dev/growomat/apis/growomat-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/growomat/apis/growomat-public-api/revisions/f02611b531aa?raw)