> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apostra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creative sync outcomes

> Read where a creative stands on each seller, who must act, and why.

Apostra sends a creative to each seller on a media buy separately. When a
creative has not reached a seller, or the seller turned it down, the creative's
`platformLinks` tell you which of those happened, who must act, and why. Read
them before you tell anyone that a seller rejected a creative: a seller rejection
is one reason among several, and in most cases the seller never saw the creative.

`get` with `kind: "creative"` returns one entry in `platformLinks` per seller.
The same read in v2 returns `platform_links`, with the names in the last column
of the tables below.

`get` with `kind: "media_buy"` and `include: ["creatives"]` also returns
`failureReason` on an attached creative when its delivery was not sent or
failed. It uses the same closed reason set as `platformLinks`, so a delivery
failure does not become a seller rejection just because it appears on a media
buy.

When an operation cannot start a creative send, `get` with `kind: "media_buy"`
and `include: ["operations"]` reports its classified state and next action. It
stays pending while Apostra retries, then reads as failed when retrying stops.
Apostra retains the diagnostic for support and escalations; do not treat
`send_failed` as a seller review or change the creative unless support
identifies a creative-specific refusal.

## A buy books without creatives the seller has not accepted

A creative the seller has not accepted does not stop a media buy booking. Apostra
books the buy without that creative and holds its assignment. The creative is not
sent to the seller as part of the booking, and the booking does not fail, retry or
raise an alert because of it. Until the seller accepts it, a campaign-wide change
to the buy's creatives leaves the held creative out.

A held creative says who has to act and why. `get` with `kind: "media_buy"` and
`include: ["creatives"]` returns `held` on each creative the buy booked without:

| `held.state` | `held.owner` | What it means |
| - | - | - |
| `pending_review` | `seller` | The seller is still reviewing the creative. Nothing is needed from you. |
| `seller_rejected` | `buyer` | The seller rejected the creative. Replace or correct it. The seller's reason is in `rejectionReason`. |
| `superseded` | `buyer` | A newer revision replaced the one under review. Send the current revision. |

A creative that is not held, or has no `held` field, is attached to the buy as
usual. When a buy never had a creative and books with none, the seller reports it
as `pending_creatives` until creatives are attached.

### When every creative is held

Some sellers refuse a booking that carries no creative at all, and that refusal is
final: the buy is lost. Others accept it and hold the buy in `pending_creatives`
until creatives are approved, which AdCP treats as valid. Apostra tells them apart
from certification: a seller whose latest `create_without_creatives` check passed
on every inventory source the buy routes to accepts a buy created with no creatives
(see [Create without creatives finding](https://docs.apostra.com/v3/certification.md#create-without-creatives-finding)).
A source run by Apostra's embedded sales agent needs no check: the agent declares the
answer for its ad server, and Apostra reads that declaration instead. A source that refuses a buy booked this way is treated as not accepting one for seven days, so the next buy to it waits for the seller's review instead, and Apostra looks into the refusal.

A creative that fits none of the buy's products is left off the booking and
reported, and does not count here: a buy whose only fitting creatives are held is
treated the same as a buy whose every creative is held.

What happens when withholding the held creatives would leave a buy with none
depends on that and on who has to act:

* **Every creative is `pending_review` and the seller has passed that check.** The
  buy books now with no creative, so you do not lose flight days to the review. The
  creative stays held, owned by the seller, and Apostra attaches it when the seller
  approves it, as described below. If you set
  `startRequiresAllCreativesApproved: true` on the line item, the buy waits instead,
  as in the next item. The campaign launch preview says the same: it does not list
  `CREATIVE_NOT_READY` for a creative that is only waiting on that review, and it
  names the buy as one that books now with the creative attaching on approval. A
  rejected, missing or failed creative is still listed.
* **Every creative is `pending_review` and the seller has not passed that check**,
  because it failed, was inconclusive or has not been probed yet. The seller owns the
  wait. The buy is held, not failed and not retried, and Apostra books it as soon as
  the seller accepts a creative. If the seller rejects the creative instead, the buy
  is re-checked and refused as below. A campaign launch reports such a buy as
  waiting on the seller, with the code `CREATIVE_REVIEW_PENDING`, recovery
  `transient`, how many creatives are in review, and since when: when the seller
  took them into review on a Storefront hosted on Apostra, otherwise when they were
  last sent for review.
* **Any creative is `seller_rejected` or `superseded`.** You have to act, and a
  buy never waits on you, whatever the seller's certification shows. The booking is
  refused before anything reaches the seller, with the code `INVALID_REQUEST`, the reason `CREATIVE_ACTION_REQUIRED`,
  `owner: buyer` and `recovery: correctable`, naming the creatives. The buy stays a
  draft. Fix or replace the creative, then execute again.

A buy with at least one creative that is not held books with it, and holds the
rest as above.

When the seller accepts a held creative, Apostra attaches it to the booked buy
and `held` goes away. The attach is the same one you would make yourself, so the
seller is asked again and the creative reaches the buy only if the seller still
takes it. A creative is attached only when Apostra can tell that the seller
accepted the exact revision that was held, on the seller account the buy was
booked on, for every inventory source the buy routes to, from the answer
Apostra records for that creative on the route. A route that records no answer
per creative (a Storefront-level route with no inventory source and no adapter)
never releases automatically; assign the creative yourself there. In any other
case it stays held, with its owner, rather than being attached on a guess. On a live buy
whose seller did not declare that it takes creative assignments, an accepted
creative also stays held.

Only a creative that is waiting on a review is held. A creative Apostra could not
send because its own format matches nothing the seller offers, or one with no
review recorded at all, still stops the booking with its reason, because a review
will not settle it.

## A creative added to a live buy waits for the seller's review

When you add a creative to a media buy the seller has already booked, and the
seller takes the creative into review, the delivery waits on that review instead
of failing. Nothing is needed from you. `get` with `kind: "media_buy"` and
`include: ["operations"]` shows the delivery as `blocked` with
`blockedReason: CREATIVE_REVIEW_PENDING` and no `nextAction`. Apostra sends it
again about 30 seconds after the seller's verdict arrives, whether by the
seller's callback or in its answer to a later send of the creative, so verdicts
on several creatives go out in one send.

* **The seller approves the creative.** The delivery is sent and the creative
  reaches the buy.
* **The seller rejects the creative.** The delivery stops with
  `recovery: correctable` and you get a media buy notification. Apostra does
  not send the rejected version to the seller again, and updating a buy that
  carries it is refused, naming the creative, until you correct or replace it.
  Then add it to the buy again.
* **The seller never answers.** The delivery keeps waiting and stays `blocked` on
  the buy's operations. Once the buy has ended or passed its flight, the
  operation is closed. For 7 days after a buy completes, Apostra still reads it
  from the seller once an hour, only to collect a creative review the seller
  gives late; that read never changes the buy, and after 7 days Apostra stops.
  If the seller still has not decided by then, and no other buy with that
  seller carries the creative, the review lapses and the creative stops reading
  `pending_review` for it (see
  [When a seller's review lapses](https://docs.apostra.com/v3/creative-sync-outcomes.md#when-a-sellers-review-lapses)).
* **The seller ends its review without deciding.** When the seller says the
  creative failed in a way a retry might clear (every error `transient`),
  Apostra sends the delivery again after a wait. If the seller takes the
  creative into review again with no decision, Apostra counts that send and
  waits longer before the next one. After five such sends the delivery fails,
  owned by Apostra, and Apostra looks into it. A send made because the seller
  approved a creative the delivery was waiting on is never counted.

A platform adapter whose platform reviews a creative only once an ad uses it,
such as Google Ads, is not held this way.

## Say whether a line item may start before every creative is approved

By default Apostra books a buy with the creatives the seller has approved and
attaches the rest as their reviews clear, so a line item can start delivering with
only some of its creatives. To rule that out for a line item, set
`startRequiresAllCreativesApproved: true` on that line item in `save_media_buy`
when you create the buy. Apostra holds the buy itself until every creative on the
line item is approved; the table below says what that means.

| Value | What happens when a creative on the line item is still in the seller's review |
| - | - |
| `false`, or not sent | The buy books with the approved creatives. The creative in review is held and attached when the seller approves it, as described above. |
| `true` | The buy does not book. It waits, owned by the seller, and Apostra books it once every creative on the line item is approved. Other creatives on the line item that are already approved do not change that. This holds whatever the seller's certification shows. |

With `true`:

* **A creative in review (`pending_review`).** Nothing is sent to the seller. The
  buy is held, not failed and not retried, and Apostra checks it again when the
  seller's answer for a creative arrives. It books when none is left in review.
* **A creative you must fix (`seller_rejected` or `superseded`).** The buy does not
  wait on you. The booking is refused before anything reaches the seller with the
  code `INVALID_REQUEST`, the reason `CREATIVE_ACTION_REQUIRED`, `owner: buyer` and
  `recovery: correctable`, naming the creatives. The buy stays a draft; fix or
  replace the creative, then execute again.
* **A line item with no creatives.** There is nothing to wait for, so the buy books
  and the seller reports it `pending_creatives` until creatives are attached.
* **Another line item.** A creative in review on a line item that is not set to
  `true` does not hold the buy. It is held and attached later, as above.
* **A line item whose creatives Apostra cannot tell apart.** Apostra normally knows
  which creatives each line item carries. If a line item set to `true` has no
  creative assignments recorded at all, Apostra cannot say which creatives are
  its own, so it counts every creative in review on the buy as belonging to it and
  holds the buy. That is the cautious reading of "do not go live before every
  creative is approved".

Apostra does not ask the seller to hold the line item as well. AdCP 3.3 once let a
package carry `start_requires_all_creatives_approved` on a media buy create, and the
3.3.0-beta.6 preview removed it from create and update; it stays on the seller's
`control_media_buy` package controls. Apostra does not use those controls yet, so the
wait before booking is the whole guarantee. It books only when every creative on the
line item is approved, so the seller never starts the line item with some of them.

Set the flag when you create the buy. Sending it on an update returns
`NOT_IMPLEMENTED`; it cannot be changed on a booked buy yet.

The status you read for the buy is the one the seller reports, as AdCP defines it.
`pending_creatives` means no creatives are assigned. `pending_start` means
creatives are assigned and the buy is waiting on their review or on its start date.
A buy that Apostra is holding has not reached the seller yet, so it has no seller
status.

## Creative lifecycle status

V3 creative reads include an AdCP `status` alongside the existing creative
fields. Apostra derives it when you read the creative; there is no separately
stored lifecycle value. The result uses the first matching row below, in order.

| Stored value | AdCP `status` | What it means |
| - | - | - |
| The creative is archived | `archived` | The creative is archived, regardless of its authoring state or seller approvals. |
| Any platform link has raw `approvalStatus: "rejected"` or `"changes_requested"` | `rejected` | A seller rejected the creative or asked for changes. AdCP has no separate lifecycle value for a change request. |
| Any platform link has raw `approvalStatus: "pending"`, `"pending_review"` or `"partially_approved"`, other than a review that lapsed (see below) | `pending_review` | At least one seller still needs to complete review. A partly approved creative is not reported as fully approved. This can appear while the campaign is still a draft (see below). |
| Every recorded platform-link approval is `"approved"`, leaving out a review that lapsed | `approved` | Every seller that has recorded an approval approved the creative. |
| Stored `assembly_state` is `draft` or `complete`, with no more specific result above | `processing` | The authoring state does not say where seller review stands, so the read does not claim more precision. A creative whose only seller reviews lapsed with no verdict reads `processing` too: the review closed without a decision, and none is coming. |
| No stored value | `suspended` | This value cannot be returned today because no stored creative state represents suspension. |

The precedence is `archived`, then `rejected`, then `pending_review`, then
`approved`, then `processing`. This means one rejection outranks another
seller's approval, and an archive marker outranks every approval.

### When a seller's review lapses

A seller can take a creative into review and never decide, for example when
the only media buy it was sent for ends first. Apostra reads a completed buy
from the seller for 7 days to collect a late verdict (see "The seller never
answers" above). After that the review lapses, and the creative's `status` no
longer counts it as `pending_review`.

A seller's review lapses when all of these hold:

* the seller has given no verdict: the link's `approvalStatus` is `pending` or
  `pending_review`;
* every media buy that carries the creative at that seller has ended
  (completed, canceled, failed, rejected or archived), and the last of them
  ended more than 7 days ago;
* Apostra recorded nothing new on that seller's link after those buys ended,
  such as a new send of the creative or a callback from the seller.

What you see when a review lapses:

* **The seller's link stays.** It is still in `platformLinks`, with
  `approvalStatus` as the seller left it, because that is still what the seller
  holds.
* **Other sellers decide the `status`.** With no other verdict the creative
  reads `processing`. If every other seller approved it, it reads `approved`,
  and a rejection elsewhere still reads `rejected`.
* **Search agrees.** `search` with `filter.statuses` applies the same rule.
* **Sending the creative to that seller again reopens the review.** A resync, a
  send through `sellerIds`, or a new media buy with that seller that carries the
  creative opens it again, and the creative reads `pending_review` until the
  seller decides.
* **A creative sent with no media buy never lapses there.** A send through
  `sellerIds` or `sendCreativesToConnectedSellers` has no buy to end, so that
  review stays open.
* **v2 creative reads do not change.** They have no creative-level status, and
  `platform_links[].approval_status` still shows what the seller holds.

A review waiting in a seller's own Apostra review queue does not lapse.
Apostra closes it instead, once every media buy the creative was sent for to
that seller has ended and the review has waited a day. The seller's link then
reads `approvalStatus: "rejected"`, so the creative reads `rejected`, and its
`rejectionReason` is "Expired: the media buy ended before the seller reviewed
this creative, so it was not delivered." This is Apostra's reason, not the
seller's verdict, and a seller approval made after it is not recorded. Send the
creative again with your next media buy with that seller to have it reviewed.

### Review starts before the campaign launches

A creative on a draft media buy is sent to that buy's seller as soon as you save
it, so the seller's review runs while you finish the campaign rather than after
you launch it. The creative can therefore read `pending_review` while the
campaign is still a draft. That is the seller reviewing the creative only: the
media buy is not booked and nothing delivers until the campaign is launched.
Read the creative's `platformLinks` to see which seller has it. A creative that
reads `processing` and has no platform link has not reached a seller yet.

A seller connected through a direct ad-platform adapter works differently:

* **Meta, TikTok, Snap and OpenAI Ads** take the creative into the ad account
  before the media buy launches, and its link then carries the platform's own id
  for it in `platformId`. Holding it is not approval. These platforms review
  policy on the ad, which they create when the media buy launches. Before
  launch they have only checked the creative's format and that Apostra may place
  it in that account, so their policy review, and any rejection, comes at
  launch.
* **Amazon, Google, LinkedIn, Pinterest, Reddit and Spotify** take a creative
  only as part of a booked campaign. Apostra sends them nothing before the media
  buy launches, so until then the creative has no link to that seller. That is
  expected, not a failure.

### Send a creative to sellers before any buy

You can put a creative in front of sellers before you have a media buy with
them, so their review can finish before you buy. Send `sellerIds` on
`save_creative`: the seller ids from `search(kind: "seller")`, up to 200.

```json theme={null}
{ "creativeId": "cr_123", "advertiserId": "42", "sellerIds": ["101", "205"] }
```

* **The list replaces the sellers you named before.** Send `[]` to name none.
  Leave `sellerIds` out to keep the list as it is.
* **Each seller is sent the creative on its own,** with no media buy, and again
  each time you save a new version of it. A draft is not sent: the sellers get
  it when you complete the creative.
* **You only name sellers.** Whatever runs behind a seller (an ad platform, a
  managed sales agent or the seller's own agent), you name it the same way.
* **The send uses your account with that seller** for the creative's
  advertiser. If that account is still being set up, the send waits, and
  `platformLinks` shows that seller with `failureReason: "account_not_linked"`
  (`not_sent`, Apostra to act). It goes out on its own once the account is
  ready. If no account is being set up, the creative is not sent and reads
  the same way; save the creative again once your account with that seller
  is ready.
* **Removing a seller from the list** withdraws your pending review there, and that seller no longer appears on `platformLinks` as reviewing the creative,
  unless a media buy with that seller still carries the creative. The
  withdrawn review no longer counts toward the creative's `status`, in a read
  or in `search` with `filter.statuses`. Archiving the creative withdraws it
  from every seller the same way.
* **A seller that has already approved the creative keeps its copy.**
  Removing the seller, or archiving the creative, withdraws only a review
  that is still pending. A seller's own sales agent keeps an approved
  creative in its library: AdCP does not yet define a request that archives
  one creative at a seller, so Apostra does not send one. An ad platform
  that takes creatives without a buy, such as Meta, TikTok or Snap, receives
  the creative in your ad account, and that copy stays in your ad account
  for now: Apostra does not yet remove it.
* **A media buy still carries the creative to its seller as usual.** Where a
  live buy with a seller carries the creative, that buy's copy is the one the
  seller keeps.

`save_creative` refuses `sellerIds`, before saving anything, when:

| Refusal | Why | What to do |
| - | - | - |
| `NOT_FOUND`, naming the ids | You cannot see that seller. | Use `search(kind: "seller")` for the seller ids available to you. |
| `VALIDATION_ERROR` on `sellerIds`, naming the ids | That seller takes a creative only together with a media buy: for example Google, Amazon, LinkedIn, Pinterest, Reddit and Spotify, or a seller whose agent says it keeps no creative library. | Assign the creative to a media buy with that seller. |
| `VALIDATION_ERROR` on `sellerIds` | The creative is reference material, which is never delivered. | Make it evergreen first. |

`sellerIds` cannot be sent with `resync` or `isArchived: true`, and only a
buyer account can send it. `get(kind: "creative")` returns the creative's
`sellerIds`, `[]` when there are none. Each seller's answer appears on
`platformLinks` like any other send.

### Send an advertiser's whole library to its connected sellers

Rather than naming sellers on each creative, you can turn on one switch on the
advertiser. Send `sendCreativesToConnectedSellers: true` on `save_advertiser`:

```json theme={null}
{ "advertiserId": "42", "sendCreativesToConnectedSellers": true }
```

* **Which sellers.** Every seller you are connected to where this advertiser
  has an ad account linked, and that takes a creative without a media buy.
  Sellers that take creatives only with a buy (the ones `sellerIds` refuses)
  are left out.
* **Which creatives.** Every complete, unarchived creative in the advertiser's
  library, except reference material. Each is sent the way a seller named in
  `sellerIds` is: on its own, with no media buy, and again each time you save a
  new version of it.
* **It keeps up.** A creative you add or complete later is sent too. When you
  link an ad account at another seller, that seller is sent the whole library.
  When you unlink the account or archive your connection to that seller, the
  sends the switch made there are withdrawn.
* **Turning it off** with `false` withdraws the sends the switch made, the same
  way removing a seller from `sellerIds` does. A creative that names that
  seller in `sellerIds`, or a media buy with that seller that carries it, keeps
  it there.
* **Changes take effect within about a minute.** The sends run in the
  background, and each seller's answer appears on the creative's
  `platformLinks`.

A new advertiser starts with the switch off. `get(kind: "advertiser")` returns
`sendCreativesToConnectedSellers` and `creativeSyncSellerIds`, the sellers the
switch currently sends to (`[]` when it is off, when the advertiser is archived,
or when no seller qualifies).

### Per-platform approval status

Each entry in `platformLinks` keeps its raw `approvalStatus`. Its
`approval_status` alias uses AdCP's approval terms:

| Raw `approvalStatus` | `approval_status` |
| - | - |
| `pending` or `pending_review` | `pending_review` |
| `approved` | `approved` |
| `partially_approved` | `partially_approved` |
| `changes_requested` or `rejected` | `rejected` |

If a raw value has no faithful AdCP equivalent, Apostra keeps the raw value and
leaves `approval_status` out rather than guessing.

## Creatives a seller approves automatically

A seller can set its storefront to approve creatives automatically, and a seller connected through a direct ad-platform adapter (for example Meta or OpenAI Ads) is always automatic, because the platform does its own review. For a seller
that also has automatic delivery turned on (a beta setting), `sync_creatives`
does not wait for the seller's platform. The creative is recorded as approved by
the storefront's setting, with no reviewer and no review task, and `sync_creatives`
answers `processing` for it. Apostra then delivers it to the seller with the same
retries and follow-ups as a creative a person approved. It settles later: the
platform link moves to `approved` when the seller's platform reports the creative
approved, or to `rejected`, with the platform's own words, when it refuses it. A
seller without the setting still gets the answer its platform gives inside your
call.

While a creative waits on the seller, the media buy it is assigned to stays in
`pending_creatives`. Apostra still sends the buy with the creatives that are ready
and does not hold the launch for the rest. A creative that does not declare
exactly one format stays `pending_review` until a person at the seller reviews it,
as it does for a seller who reviews every creative.

## Creatives you sync to a direct ad platform

A creative you sync to a seller connected through a direct ad platform, such as
Spotify, can read `pending_review` while the platform reviews it. Apostra reads
the platform's decision the next time it reads the status of a campaign that
uses the creative, and applies it when the seller reports your creative's own
`creative_id` in `creative_approvals`, as AdCP requires. The creative then moves
to `approved` or `rejected`, and a campaign waiting on its review is released.
Some of our ad-platform adapters report the platform's own id there today and
are being fixed; until they are, the creative stays `pending_review` for those
platforms. As for any seller verdict, Apostra keeps a fixed summary of a
rejection, not the platform's own words. A creative the platform has already
approved or rejected is not changed by a later read, and a creative the
platform still reviews stays `pending_review`.

### Creative ids from ad-platform connections

When a seller's direct ad platform answers `creative_approvals` (on a media buy
read) or `list_creatives`, it names each creative by your own `creative_id`, the
id you sent in `sync_creatives`. That is what AdCP requires. The platform's own
id for the ad or creative never appears as a `creative_id`; it is in
`platform_id` or under `ext` (for example `ext.spotify.ad_ids`).

* **One creative, one review, decided the same way on every platform.** A
  platform can hold several objects for one creative: an ad per ad set, an ad in
  each campaign it runs in, or an old ad that keeps running until its
  replacement is approved. The creative appears once, with one review, and every
  ad-platform connection (Google, Meta, Pinterest, Reddit, LinkedIn, Snap,
  Spotify, TikTok, OpenAI Ads and Universal Ads) decides it by this rule:

  1. Only current objects count, meaning objects that can run. An object is
     current when the platform has not archived, deleted or removed it and
     Apostra has not replaced it: where you replaced the creative and Apostra
     recorded the new version, only the latest version counts, and on Spotify an
     ad made from older content, or one that could never run, is replaced by a
     newer ad. An object from an earlier version cannot hold the review. An
     object you paused yourself is still current.
  2. The least favourable current review wins: `rejected`, then
     `pending_review`, then `approved`. Reddit and LinkedIn are the exception,
     described below: the newest current object decides there.
  3. A tie goes to the lowest platform id, so the answer never depends on the
     order the platform lists its objects in.
  4. With no current object, the newest object by the platform's creation time
     decides. An object with no creation time ranks older than one that has it.
  5. With no current object and no creation time, nothing says which review is
     authoritative. The creative is left out of `creative_approvals` rather than
     given a guessed review, and the connection logs it. It returns as soon as
     one object is current or carries a creation time.

  In a media buy read, each package carries one review for the creative, decided
  by this rule over that package's objects. In `list_creatives`, the creative has
  one `status`, decided over all its objects, and one assignment per package
  that still holds a current object of it. Two platform differences remain.
  Spotify leaves an ad it has removed out of the review altogether, and a
  creative whose Spotify ads were all removed reads `archived` with no
  assignment. Reddit and LinkedIn give no way to tell a replaced object from a
  live one, so there the newest current object decides instead of the least
  favourable one: a newer approval replaces an older rejection, and a newer
  rejection beside an older approval reads `rejected`.
* **A creative Apostra has no record of is not listed.** A creative made
  directly on the platform, or synced through Apostra before it kept this
  record, has no `creative_id` of yours. It is left out of `list_creatives` and
  of `creative_approvals`, never listed under the platform's id. It does not
  change whether a buy counts as having creatives.
* **Existing posts are candidates, not creatives.** Meta lists a Page post, and
  TikTok lists an authorized Spark post, that you could build a creative from.
  Each appears in `list_creatives` with a `meta_existing_post_` or
  `tiktok_spark_` id, as a candidate with no review and no assignment. It never
  appears in `creative_approvals`, and it is not a creative until you sync it.
* **To bring it back, sync the creative.** Send it again with `sync_creatives`
  under the `creative_id` you want it known by. Spotify recognises its own
  existing ad and records it without making a second one. Meta makes a new
  creative on the platform, and a second ad beside the old one when you assign
  it, so remove the old ad on the platform if you do not want both.
* **Two new outcomes from `list_creatives` on Spotify.** `CREATIVE_IDENTITY_UNAVAILABLE`
  (503) means Apostra could not read its record of which ad belongs to which
  creative; it returns no list rather than an empty one that would say you have
  no creatives. Retry later. `MISSING_TENANT_SCOPE` (401) means the call carried
  no identity for the account's owner; retrying does not help, so contact
  support.

## Reading archived creatives

An archived creative remains available from `get` and returns
`status: "archived"`. To read an archived campaign creative, call `get` with
`kind: "creative"`, its `id`, and that campaign's `sourceId`. The creative must
belong to that campaign. For an advertiser-owned creative, use its
`advertiserId` instead.

To find creatives by lifecycle, call `search` with `kind: "creative"`, the
campaign's `filter.campaignId`, and `filter.statuses` containing one or more
of `processing`, `pending_review`, `approved`, `rejected`, or `archived`. The
filter uses the same mapping and precedence as the returned `status`; several
values are an OR. `suspended` is an AdCP status but cannot be selected yet:
Apostra has no stored suspension state, so the call returns `VALIDATION_ERROR`
instead of silently ignoring it.

For an archived-only campaign search, use either
`filter.statuses: ["archived"]` or `filter.isArchived: true`. Both keep the
campaign scope: a campaign search does not return another campaign's
creatives. If both selectors are present, they must agree: for example,
`isArchived: false` cannot accompany `statuses: ["archived"]`; conflicting
selectors return `VALIDATION_ERROR`.
Omitting both selectors keeps the existing default and excludes archived
creatives.

## Updating and archiving advertiser-owned creatives

To update a creative held in an advertiser Library, call `save_creative` with
its `creativeId` and the Library's `advertiserId`, without `campaignId`. You
can change its name, message, labels, or URL macro additions. Its canonical
format and media stay together. A different `formatKind` returns
`VALIDATION_ERROR` with `field: "format_kind"` and the message: "Changing a
creative format requires replacing its media. Create a new creative with the
destination format instead." Create a new creative when you need a different
format. The advertiser must belong to your account.

A campaign-scoped creative uses its `campaignId` for an update. Its established
campaign update path can accept an unpinned canonical-format change, while a
product-pinned creative returns `VALIDATION_ERROR` because its `format_kind` is
pinned by `format_option_ref`; a non-image creative changing to `image` also
returns `VALIDATION_ERROR` because image dimensions are required. The
campaign-scoped service can replace media atomically, but `save_creative` treats
media inputs as create-only, so create a new creative when changing media or
format through this tool.

To archive an advertiser-owned creative, call `save_creative` with
`creativeId`, `advertiserId`, and `isArchived: true`. An archived creative is
not returned by the default read, but remains available as described above.
Reading it returns `status: "archived"` and `lifecycle.isArchived: true`, both
from the same archive marker.

## Whether the creative is synced everywhere

`lifecycle.synced` on the creative (v2 `sync_status.synced`) is `true` when the
creative is synced at every seller that still takes it, and `syncedAgentCount`
(v2 `sync_status.agent_count`) counts those sellers. A media buy carries the
creative when one of its packages is assigned the creative, or the buy belongs
to a campaign the creative is attached to. A failed or pending link to a seller
where every media buy carrying the creative has ended, last tried before those
buys ended, does not hold `synced` at `false`, because nothing will send the
creative there again for them. Any other link counts, including a send made
after those buys ended and a send to a seller the creative has no media buy
with. Every link still appears in `platformLinks`.

> [!WARNING]
>
> A synced, approved creative sits in the seller's library. That is not the same
> as being attached to a media buy, and a buy can hold none while its creatives
> read as synced. A buy that would reach a seller with no creative on any package
> is refused before it is sent, with `INVALID_REQUEST` and
> `reason: "NO_CREATIVES_ATTACHED"`, naming the creatives its campaign holds that
> its products accept. The buy stays a draft: attach those creatives to it, then
> launch it again. We refuse it ourselves because a seller that requires a
> creative refuses the booking outright, and that refusal cannot be undone. A buy
> whose creatives are all waiting on the seller's review is not refused this way:
> it books now or waits for the review, as
> [When every creative is held](https://docs.apostra.com/v3/creative-sync-outcomes.md#when-every-creative-is-held) describes.

## Where the creative stands

Each seller link is in exactly one stage, or in none when there is nothing to
report (the creative is synced and approved).

| Stage | Meaning | v2 field |
| - | - | - |
| `not_sent` | The creative was stopped before it reached this seller, almost always for a reason on our side. The seller never saw it. | `sync_stage` |
| `pending` | The creative is on its way and a party is expected to take a step, such as a seller's review. It is not an error. | `sync_stage` |
| `failed` | The creative cannot get there without a correction. | `sync_stage` |

A seller can answer after we have closed the sync, for example when our request to its agent timed out or its reply listed package assignment errors. A later `approved` or `rejected` from that seller still applies: `approvalStatus` changes to the seller's verdict, and `failureReason` keeps saying that the delivery failed. We keep the first approval or rejection a seller gives for a creative on one send. A later answer that contradicts it is refused and does not change `approvalStatus`.

## Who must act

The party who must act follows the cause, not the step where it showed up.

| Party | Meaning | v2 field |
| - | - | - |
| `seller` | The seller is reviewing or processing the creative. Nothing for you to do. | `must_act` |
| `buyer` | The creative itself must change: a missing click-through URL, a format the destination cannot take, a creative the seller rejected, or changes the seller asked for. | `must_act` |
| `apostra` | Apostra must fix it. The creative is not at fault, and you cannot fix it by editing the creative. | `must_act` |

A `not_sent` creative names Apostra, except when our destination check finds that the creative's format cannot be delivered to that destination (`destination_profile_rejected`). Then it names the buyer, who needs to supply a creative in a format that destination accepts.

## Why

In v2, `sync_reason` carries the reason. In v3, `failureReason` carries it for
links that are `not_sent` or `failed`, and `pendingReason` carries it for links
that are `pending`. A live link has neither. A pending link without a recorded
reason has no `pendingReason`; read `status` and `approvalStatus` instead: a
seller reviewing the creative reads as `approvalStatus: "pending"`, and a seller
that asked for changes reads as `approvalStatus: "changes_requested"`. The raw
field stays available. The Per-platform approval status section above lists
its AdCP alias. Every reason fixes its stage and the party who must act.

A pending link settles when the seller reports its decision. The seller's
sales agent can send the decision in a callback, or announce on its account
change feed that the creative changed; we then read the creative from the seller
and settle the link from what it holds. Failing both, the scheduled check settles
it. Whichever arrives first settles the link, and you are told once.

If none of those arrives, Apostra asks again by sending the creative to the
seller again. Whether that is safe depends on the platform. Spotify,
Reddit and Meta reuse the ad an earlier send made when the creative has not
changed, so Apostra sends the creative again each time it next syncs the buy's
creatives, and on the hourly status read of the buy while the platform's review
of the buy's creatives does not name it, and the platform's finished review is
read back. A creative whose
content did change is not reused: Reddit makes a new ad for changed text and
refuses an edited image, video or carousel, and Meta makes a new creative. A
Reddit text creative first sent before Apostra recorded its content gets one
more ad on its next send, then keeps that one. Every other seller gets the creative
again only after seven days, because a repeat send could make a second ad or
creative. That send is the last: if it also goes unanswered, Apostra does not
send the creative again while the seller still has it in review.

When the seller rejects a creative and says why, the v2 creative's
`platform_links[].rejection_reason` is the seller's review reason, word for
word, and the sync row's AdCP `errors` are the errors it returned. Each string is
at most 500 characters of plain text; a longer one, or one with markup or control
characters, is left out whole rather than cut short. Treat it as the seller's text,
not ours. When the seller gives no reason, the message you see is the one you saw
before. V3 `platformLinks[].rejectionReason` is unchanged and does not carry it.

The exception is a storefront that reviews creatives automatically. When its
reviewer rejects a creative, `rejectionReason` (v2: `rejection_reason`) is the
reviewer's own reason, written by Apostra rather than the seller, and begins
`Rejected automatically:`. It is plain text of at most 700 characters and says
whether the creative can be fixed. If it can, the reason says what to change and
that you can resubmit. If the storefront does not accept this kind of ad at all,
it says so and that resubmitting will not help. It may quote or paraphrase the
seller's Creative Policy, and may end with the rule applied, as
`Policy rule: "..."`. See [Creative approval](https://docs.apostra.com/v2/buyer/creatives/approval) for
what to do next.

| Reason | Stage | Who must act | What happened |
| - | - | - | - |
| `account_not_linked` | `not_sent` | `apostra` | The account for this seller is not linked or not ready, so we did not send the creative. |
| `client_setup_failed` | `not_sent` | `apostra` | We could not set up the connection to this seller. |
| `format_unresolved` | `not_sent` | `apostra` | We could not work out which of the seller's formats the creative belongs to. |
| `request_invalid` | `not_sent` | `apostra` | The request we built for this seller failed our own checks before it was sent. |
| `destination_profile_refused` | `not_sent` | `apostra` | We have not certified the destination for this kind of creative, or we owe the destination a rendition of it, so the destination rules refused to forward the creative. The seller was never called. |
| `destination_profile_rejected` | `not_sent` | `buyer` | Our destination check found that the creative's format cannot be delivered to the seller's destination, so we did not send it. The seller was never called. Supply a creative in a format that destination accepts. |
| `click_through_unverified` | `not_sent` | `apostra` | We could not verify the creative's click-through destination and did not send it. Syncing again retries the check. |
| `send_failed` | `not_sent` | `apostra` | Our attempt to send the creative did not complete. |
| `awaiting_seller_review` | `pending` | `seller` | The seller has the creative and has not yet decided. |
| `seller_requested_changes` | `pending` | `buyer` | The seller asked for changes before it will approve the creative. |
| `click_through_required` | `failed` | `buyer` | The creative has no click-through URL, or no destination in its VAST document, and we do not send a creative without one. |
| `landing_page_invalid` | `failed` | `buyer` | The landing-page URL is not an HTTP or HTTPS address. |
| `creative_refused` | `failed` | `buyer` | We refused the creative before sending it because it cannot be delivered as submitted. Copy in a text slot that is longer than the seller's API accepts ends here. |
| `booked_products_not_readable` | `failed` | `apostra` | We could not read a booked product needed to project this creative to a legacy seller. The error names the unread product IDs. The seller never received the creative; Apostra must restore the catalog record before it can sync. |
| `seller_rejected_content` | `failed` | `buyer` | The seller reviewed the creative and rejected it. This is the only reason that means the seller rejected the creative's content. |
| `seller_rejected_request` | `failed` | `apostra` | The seller refused how we sent the creative, for example an invalid request, an account it does not know, or a change it does not accept, such as an edit to a creative it is already serving. It gave no verdict on the creative. |
| `seller_error` | `failed` | `apostra` | The seller returned an error or did not process the creative. It gave no verdict on the creative. |

The set is closed. A link with no reason has nothing to report, or was last
written before reasons were recorded; it fills in the next time the creative is
sent to that seller. A creative the destination check rejected earlier may still read
`destination_profile_refused`, naming Apostra, until it is sent again.

### When the seller has not accepted your account yet

`account_not_linked` also covers a seller that is still setting up or reviewing
your account with it. Apostra resends these creatives itself once the seller
reports the account active:

* a creative saved onto, or edited on, a draft media buy;
* a creative resent because its click-through parameters changed.

Apostra also waits while it is still setting up your account with a seller.
A creative on a draft media buy for that seller is held until the account is
ready, then sent under it, so the seller reviews it once. If the setup ends
without an account, the creative is sent as it would have been without one.

You do not need to sync them again. Apostra waits only when every part of
that seller it tried to reach is waiting on your account. If another part of
the same seller refused the creative for a different reason, Apostra reports
the creative as not sent straight away instead of waiting. If the seller
refuses or closes the account, Apostra stops waiting; contact the seller. Other creative sends
stopped this way are not resent on their own, so sync the creative again once
the seller accepts the account.

### When a Meta ad account has no Facebook Page

Meta publishes an ad as a Facebook Page, so it refuses every creative sent to an
ad account that has no Page authorized on it. Apostra stops the creative before
creating anything on Meta and reads it as `creative_refused`. The cause is the ad
account, not the creative, so replacing the creative does not help.

The campaign's `readiness.blockers` entry for the creative and the error a
campaign launch returns both quote the action: connect a Facebook Page to the Meta
ad account in Meta Business Settings, then launch again. A launch sends the
creative again, so there is nothing else to resend. Someone with admin access to
the ad account's Meta Business has to connect the Page.

An ad account with more than one authorized Page is a different case: send the
`pageId` of the Page to use, or [link the advertiser's Facebook
Page](https://docs.apostra.com/v3/advertiser-owned-links.md#link-a-facebook-page) once so creative sessions
use it when no Page is named.

### Sending a creative again

`save_creative` with `creativeId`, `advertiserId` and `resync: true` sends one
creative again to every seller it is on a media buy with, and to every seller
you named for it with `sellerIds`. Its campaign membership and its `sellerIds`
do not change. The result lists each of the creative's campaigns:

* **Live buys** (active or paused) are sent to straight away, and Apostra waits
  for each seller's answer. `status: "confirmed"` lists them in `mediaBuyIds`;
  `status: "failed"` gives the seller's error and whether retrying can help.
* **Draft buys, and buys waiting for the seller to approve them,** have the
  send queued. Their ids are in `queuedMediaBuyIds`, and each seller's answer
  arrives later on the creative's `platformLinks`. A campaign with only these
  buys reads `status: "queued"`, which is not an error.

A campaign with no buy at all still fails: there is no seller to send to.

The sellers named in `sellerIds` have the send of the creative alone queued.
Their ids are in `queuedSellerIds`, `[]` when there are none, and each seller's
answer arrives later on `platformLinks`. When a seller send is queued, the
call is not an error even if every campaign failed, and a creative on no
campaign can be resynced to its named sellers. A creative with no campaign and
no named seller is refused with `VALIDATION_ERROR`.

A campaign resync (`campaignId` and `resync: true`) sends only to media buys,
not to the sellers named on each creative.

### When the seller fails a sync that holds several creatives

A seller can fail the whole `sync_creatives` task and still return a result for
each creative it handled. Apostra settles each creative from its own result: a
creative the seller refused reads as refused, with the seller's own error for
that creative, and a creative the seller accepted reads as accepted.

A creative the failed task never mentions is not a refusal. Apostra does not
record the seller's failure against it. A creative the seller had already
approved at its current content keeps that approval. A creative that was not
approved yet reads `not_sent` with the reason `send_failed`, because the seller
gave no answer for it, and Apostra sends it again on a later pass. When the failed task carries no per-creative result at all, or none
of its results refuses a creative, every creative in the request fails as it
did before.

A seller can also fail a single creative and mark every error on it
`recovery: "transient"`, for example when its ad server briefly could not save
the change. That is not a refusal. Apostra records no rejection, leaves the
creative's approval as it was, and sends the creative again on a later pass.
Until then the creative's link reads `failed` with the reason `seller_error`.
For a creative on a media buy, each later pass waits longer after a failed
send: 2, 4, 8, 16, 32 and then 60 minutes. If the first send of the same
version to a buy and six more all fail with an answer from the seller, Apostra
stops sending it to that buy and looks into it. Editing the creative starts
the count again. A send the seller never answered is not counted: one that
failed on Apostra's side, could not reach the seller, or was turned away
because the seller's agent did not accept Apostra's credential (for example an
HTTP 401). Apostra keeps sending that creative, at most every 60 minutes, so
it reaches the seller once the cause is fixed. A
seller that fails a package assignment this way also lists the package in the
result's `assignment_errors`. That does not make it a refusal when a transient
error's `details.assignment_errors` names the same package. If any error on the
result is `terminal`, or the result lists
a package no transient error covers, or it reports an empty `assigned_to`,
Apostra does not send the same version again: the creative's link reads
`failed` with the reason `seller_error`, and Apostra looks into it. That is
still no verdict on the creative's content, so its approval stays as it was
and you get no rejection notice. Only a `rejected` review status or a
`creative_rejected` error means the seller rejected the content
(`seller_rejected_content`).

An error with no `recovery` is read the way AdCP tells a receiver to read it.
A standard AdCP error code takes the recovery AdCP registers for it: for
example `SERVICE_UNAVAILABLE` and `RATE_LIMITED` are `transient`,
`VALIDATION_ERROR` and `UNSUPPORTED_FEATURE` are `correctable`, and
`ACCOUNT_SUSPENDED` is `terminal`. A code AdCP does not register reads
`transient`, so Apostra sends the creative again on a later pass, within its
limit on resends. A seller on AdCP 3.2 or later must state `recovery` on every
error, and one on 3.1 should.

A storefront on Apostra answers the same way when it approves a creative but
cannot deliver it to the inventory behind it. Its `failed` result carries the
error code `delivery_failed` with an AdCP `recovery`: `transient` when sending
it again may succeed later, `correctable` when the request must change first,
for example an edit the inventory cannot apply to a creative it is already
serving, and `terminal` when neither helps until someone acts. It never names
the inventory source. When that inventory rejects the creative in its own
review, the storefront answers with a `rejected` review status, which reads as
a rejection of the content.

When one buy spans several inventory sources and one of them refuses a creative that
another took, the storefront does not answer `failed` for the whole creative. It answers
with the action of the sources that took it, lists the packages they assigned in
`assigned_to`, and names each refused package, with the source's reason, in
`assignment_errors`. Apostra reads a creative whose every missing package is named that way as
accepted for the packages that took it, and keeps the refusal of the named packages on the
creative's sync record. If no source took the creative, or a missing package is not named, the
result stays `failed` as before.

### When the seller says the request must change

A seller can fail a creative and mark its errors `recovery: "correctable"`: it
refused the request, and the request must change before it is sent again. For
example, a seller that cannot change a creative it is already serving refuses
the edit this way. That is not a verdict on the creative's content, so Apostra
does not record a rejection. The creative's link reads `failed` with the reason
`seller_rejected_request`, and the creative's own status and `approvalStatus`
stay as they were.

This holds when every error on the result is `correctable` or `transient` and
at least one is `correctable`, each read as above when it states no
`recovery`. A `terminal` error reads `seller_error` instead, as above. A `rejected` review status
or a `creative_rejected` error reads as a rejection of the content.

The same holds when the seller refuses the whole request rather than one
creative: a storefront on Apostra gives each creative the seller's error, with
the `recovery` the seller stated on it, so each creative's link reads as above.

The seller's own code and `recovery` are in `seller_errors` (v3:
`sellerErrors`), and its message, when it gave one we keep, in
`seller_acknowledgement`; see [What the seller reported](https://docs.apostra.com/v3/creative-sync-outcomes.md#what-the-seller-reported).
Read them to see what the seller needs changed.

Apostra does not send the refused version to that seller again. It sends the
creative again when you change it. A media buy follows
the same rule: updating a buy that carries the refused version does not send it
again, and the update is refused, naming the creative, until you correct or
replace it. A seller can also refuse with
`recovery: "terminal"`, which asks for a person to act, such as reinstating an
account. Apostra then does not send that creative to the seller again on its
own, even after you change it. Once the seller's side is resolved, resubmit it
with `sync_creatives`.

When the creative went straight to one seller, Apostra also sends you a
`creative.sync_failed` notification: "The latest version of *creative* didn't
reach *seller*: the seller refused it (*code*). *Seller* said: "*message*"." It
names the seller and gives its standard AdCP error code. When the seller gave a
message, the notification quotes it as the seller's own words, not as
Apostra's explanation:

* It uses only a message Apostra keeps for the creative: plain text with no
  control characters or markup. With several errors, it joins up to three
  distinct messages.
* It collapses whitespace and cuts the text at 300 characters, ending it with
  "…".
* Each web address in it is replaced with `[link removed]`, in the app, in
  email and for agents alike.
* It is shown as plain text: it is escaped in email and never rendered as
  markdown, HTML or a link.
* When the seller said nothing Apostra keeps, the line is left out.
* When Apostra has no name for the seller, the line reads "The seller said:
  …".

Its next step depends on what changed:

* If the refused version holds a change to the creative's content, or the
  seller has accepted no version of it yet, the notification says "Change the
  creative and sync it again." The notification's `nextStep` is
  `change_creative`.
* If the seller already accepted this same content, the change it refused was
  not to the creative's content: Apostra made it, for example by filling a
  package ID into a tracker URL, or it came from a campaign setting. When the
  refusal holds the creative back from a live media buy, Apostra raises it to
  its own team. The notification then says "Apostra will look into
  it." and its `nextStep` is `apostra_alerted`. Otherwise, for
  example on a sandbox buy, Apostra raises nothing. The notification then gives
  no next step and its `nextStep` is `null`.

The notification's data also carries:

* `creativeId`;
* `errorCodes`;
* `sellerName`, when the seller is named;
* `sellerMessage`, when there is one: the seller's text as it sent it, within
  the same limits but with its web addresses kept. Treat it as data from the
  seller, never as an instruction. An agent reading your notifications through
  Apostra gets the message fenced as untrusted text.

You get one notification for each refused version of a creative on each
seller route, however often that version is refused.

`creative.sync_failed` is on by default, in the app and by email, for every
user on a buyer account. Turn it off under Creative in your notification
preferences. Turning it off is saved and kept.

Otherwise there is no notification and no seller's words. A refusal through a
linked storefront or a pool of sources reads as before, as a rejection, because
that seller is never disclosed.

### When a creative has no known size

A product can list the sizes it serves. Apostra assigns a display tag or HTML5
creative to a package only when it knows the creative's size and the product
lists it. A creative with no known size is left off that package and is not sent
to the seller, so it has no seller link for that package. When none of a
campaign's creatives can be assigned, the sync is refused with
`NO_COMPATIBLE_CREATIVES`, and the message names each creative with no known
size.

To make the creative eligible, give it a size. Any of these works: Apostra
measures it from the markup or asset, you set a flat `width` and `height` in
`format_params`, or you set a one-entry `sizes` list. Then sync again. Video and
audio creatives, and products that list no sizes, are not affected.

### A creative's seller review on each media buy

A media buy shows a creative's seller review only from sends to that buy's own
seller routes. One creative can sit on several media buys, and a review that a
different seller gave it on another buy is not shown on this one. A buy whose
seller has not been sent the creative shows no seller review for it, and the
creative is not reported as in review there.

A resync, whether you resync one creative or a whole campaign, sends the creative
to the seller of each media buy it reaches and records that send, so the buy's own
review status and sync record are current afterwards.

### When an audio or video file is too small to be media

Apostra refuses to send a creative whose hosted audio or video file is smaller
than 1,024 bytes. No playable file is that small, so the stored upload is
empty or cut short, and a seller would only fail it later without saying why.

The refusal happens in two places. Saving a creative from an upload refuses the
file with an `INVALID_REQUEST` that names the byte count, and nothing is
saved. A campaign send that finds such a file already stored sends nothing for
any media buy of the campaign: each buy comes back with
`errorCode: CREATIVE_ASSET_INVALID`, and the message names each creative and its
stored size.

You own the fix. Upload the file again, save the creative with the new upload,
and send again. A creative that has a stored size equal to the length of its
own URL, which older audio and video rows held in place of a real size, is not
refused on that number, because it says nothing about the file.

A creative that is still being processed is not sent either. A video upload
that is still being inspected cannot be saved into a creative until inspection
finishes.

### When a video creative goes to products of different player sizes

A seller on AdCP 3.0 or 3.1 takes one format per creative. A VAST creative has
no size of its own, because the video player sets it. So when one media buy
holds products from such a seller that take VAST at different player sizes,
for example 640x360 and 640x480, Apostra cannot yet send the creative to all of
them. The creative is `not_sent` with `format_unresolved`, and the message names
each product and the format it takes. Neither your creative nor the seller has
to change. Until Apostra can send it, book the products of each player size in
separate media buys, and the creative is sent to each.

## What the seller reported

When a seller refuses a creative in its `sync_creatives` reply, Apostra keeps
the structured part of each error it returned, so you can see what to fix
without the seller's free text. In v2, `platform_links[].seller_errors` lists
them, and in v3 `platformLinks[].sellerErrors` does, in AdCP's own field names:

| Field | Meaning |
| - | - |
| `code` | The seller's AdCP error code, for example `VALIDATION_ERROR`. |
| `recovery` | `transient`, `correctable` or `terminal`: whether retrying, correcting the request, or neither can help. |
| `field` | The path of the field the error names, for example `assets.vast_tag`. |
| `issues[].pointer` | The JSON pointer of each offending field, for example `/assets/vast_tag`. |

Each part is kept only when it can be checked, and is left out otherwise:

* `code` is kept only when it is one of AdCP's standard error codes. AdCP lets a
  seller invent its own codes, and Apostra does not pass those on.
* `recovery` is kept only when it is one of the three AdCP values.
* A path is kept only when it is plain dotted or slash-separated names (bounded
  in length) and every name in it is one Apostra knows: a field of the AdCP
  creative manifest or `sync_creatives` request, a key of the creative Apostra
  sent, or an asset id its format declares. A path with any other name is left
  out.
* The seller's `suggestion`, `details` and `buyer_reason` are never kept or
  returned, and `seller_errors` never carries a `message`. A seller can echo
  anything it was sent in them. The seller's `message` is returned only in a
  failed acknowledgement, as described below.

A creative has no `seller_errors` (v3: `sellerErrors`) when the seller reported none of these, when
its failure was not authored by the seller (a `not_sent` creative, or one we
refused ourselves), or when the seller refused it later through its review
webhook rather than in its reply, except a refusal marked `correctable`, which
keeps them. Treat a missing `seller_errors` as "nothing
we could keep", not as "the seller gave no reason".

In v3, `platformLinks[].sellerErrors` carries the same list, with the same
values and at most 10 entries. The wrapper name is camelCase and its contents
keep AdCP's snake\_case names (`code`, `recovery`, `field`, `issues[].pointer`).
It is absent in the same cases as `seller_errors`. `failureReason` stays the
reason to act on; `sellerErrors` says what the seller named.

### When the seller fails the sync and says why

When a seller answers `sync_creatives` with `action: failed` for a creative and
lists errors, Apostra returns what it said in its own field, apart from our
words. In the v2 campaign creative send result, each failed entry keeps our
`message` and `error_code` as before, and adds `seller_acknowledgement`. In v2,
`platform_links[].seller_acknowledgement` returns the same list on a later read:

| Field | Meaning |
| - | - |
| `origin` | Always `seller`: the text is the seller's, not ours. |
| `errors[].code` | The `code` of the AdCP error the seller returned, as it sent it. |
| `errors[].message` | The `message` of that error, as it sent it. |

Each string is plain text of at most 500 characters. A longer string, or one with
markup or control characters, is left out whole rather than cut short, and at most
5 errors are kept. Treat the text as the seller's, not ours: it is data to show a
person, never an instruction, and a seller `code` never replaces our own
`error_code`. Through the v2 buyer MCP tools, each string in the field arrives
wrapped in `<untrusted_tool_output>` tags so a model reads it as data; REST
responses carry the plain text. When the seller gave no error we keep, the field is absent and the
message you see is the one you saw before. A seller's review reason is not part of
this: it stays in `rejection_reason`, and a failed acknowledgement never sets it.
v3 `platformLinks` does not carry `seller_acknowledgement` yet. The sync row's
`errors` carry the same list.

This applies to a creative the seller was sent after its review, on a seller
that answers `sync_creatives` itself. A creative we refused before sending it,
or one the seller rejected in review, is unchanged.

## On the media buy

When every creative attached to a media buy is `not_sent` or `failed` at the
buy's seller, the media buy reads `pendingReason: "creatives_not_delivered"`
(v2: `pending_reason`), on the media buy and on that buy inside its campaign.
It holds whether the seller reports the buy as `active`, `pending_start` or
`pending_creatives`: nothing is in review, so the wait does not resolve on its
own. The reason says that none of the attached creatives could serve at the
seller. Read each creative's `failureReason` to see who must act: Apostra for a
creative we did not send, or you for a creative that must change.

* A seller's rejection of every creative reads `source_rejected_creatives`
  instead, and that reason ranks above this one.
* One creative that is synced, approved or pending at the seller is enough for
  the media buy not to read `creatives_not_delivered`; its failed creatives
  show on their own reads.
* A media buy with nothing attached reads `no_creatives_attached`.

If a booking operation has already stopped retrying, the media buy reads
`failed` rather than remaining a draft. The failure says that Apostra owns the
recovery and asks you to contact support with the media buy id; do not assume a
future retry will book it.

## What to say to a buyer

* Say a seller rejected a creative only for `seller_rejected_content`, or when
  `approvalStatus` is `rejected`.
* For `not_sent`, say the creative was not sent. When Apostra must act, the
  buyer does not need to change the creative. The one exception is
  `destination_profile_rejected`, where the buyer needs a different creative.
* For `buyer`, say what must change, using the reason above.
* `rejectionReason` (v2: `rejection_reason`) is only the seller's own note, or an
  automatic reviewer's reason that begins `Rejected automatically:`. A creative
  that was not sent has none.

See [Creative approval](https://docs.apostra.com/v2/buyer/creatives/approval) for the two review gates
a creative passes through after a media buy is forwarded.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.