---
title: "Validate a campaign before export"
method: POST
path: "/api/v1/campaigns/{id}/validate-export"
---

# Validate a campaign before export

`POST /api/v1/campaigns/{id}/validate-export`

## Request

- Base URL: `https://api.growomat.com`
- URL: `https://api.growomat.com/api/v1/campaigns/{id}/validate-export`
- Auth: HTTP bearer

Runs the same checks a sync runs before it exports, without calling any platform. Use it before *Trigger a sync* so a refusal shows up here rather than inside a sync record.

Returns `valid` (true when nothing blocks the export), `platforms` (the ids checked) and `findings[]`, ordered worst first: `blocked`, `unsupported`, `degraded`, `ok`. Each finding also has a `kind` that says what it *is*:

- `requirement`: something you must fix before this platform accepts the campaign.
- `transform`: the platform will receive a changed version (a clamped value, for example).
- `limitation`: a permanent trait of the platform; nothing to fix.
- `suggestion`: an optional improvement.

Only `requirement` findings need your attention. Body `platforms` defaults to the platforms the campaign runs on; naming a platform validates against it even when it is not connected.

**Errors**

- `404 NOT_FOUND`: no campaign with this id in the active Space.
- `400 UNKNOWN_PLATFORM`: a platform id in the body does not exist.

## Path parameters

- `id` string, required

## Headers

- `X-Space-Id` string

## Request body

- ValidateExportRequest: Which platforms to validate against.
  - `platforms` string[]: Platform ids to validate against, for example `google-ads`. Defaults to the platforms the campaign runs on.

## 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)