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

# Hold or resume new business

> Stop or restart new buyer business on your Seller Account with the isPaused and expectedIsPaused fields on save_seller.

The intake hold stops new buyer business on your Seller Account without
touching anything already running. You set it with two fields on
`save_seller`: `isPaused` and, optionally, `expectedIsPaused`.

While the hold is on:

* Buyers no longer find your products in discovery.
* New media buys and buyer edits are refused.
* An approved buy that has not yet reached a source waits, and goes out when you
  resume. The one exception is a sandbox order from your own organization, below.

You can still test your own products while the hold is on. A sandbox
advertiser of your own organization can find your active products, stage and create a media buy, edit
it, and cancel it, with no spend. The section "Test your own products while the hold
is on" below says how.

The hold does **not** pause campaigns that are already delivering in your ad
server. They keep delivering and reporting. Resuming clears only the hold. It
does not clear any other readiness blocker, so a Seller Account that is not
ready stays `blocked` after you resume. See
[Seller readiness](https://docs.apostra.com/v3/seller-readiness.md).

The hold is separate from `apostraParticipation`, the choice to take part in
being bought through Apostra. Changing one never changes the other.

## Hold or resume

Send `isPaused` alone. `true` holds new business and `false` resumes it.

```json theme={null}
{
  "isPaused": true,
  "expectedIsPaused": false
}
```

`expectedIsPaused` is the hold you last read. Send it so a change someone else
made after your read is not overwritten.

| Field | What it holds |
| - | - |
| `isPaused` | `true` to hold new business, `false` to resume it. |
| `expectedIsPaused` | Optional. The hold you last read. If the stored hold is different, the call is refused with `CONFLICT`. |

To read the current hold, call `get_status`. A Seller Account whose `state` is
`paused` has the hold on. `live` and `blocked` mean it is off. `archived`
overrides both.

## Test your own products while the hold is on

A hold stops buyers. It does not stop your own organization. While the hold is
on, a sandbox advertiser can place a sandbox order on your Seller Account from
two places: the Seller Account itself, or a buyer account in the same
organization. Discovery returns your active products, you can stage and create a
media buy, edit it, and cancel it with `save_media_buy` and `isCanceled`. This
lets you see your own product book into your ad server before you open to
buyers. Sandbox buys spend nothing. If your storefront reviews media buys by
hand, you approve the sandbox order in your Approvals queue as usual and it goes
out to your ad server at once; any other approved order keeps waiting for the
hold to end. The steps are in
[Test your own storefront with a sandbox order](https://docs.apostra.com/v3/seller-first-booking.md#test-your-own-storefront-with-a-sandbox-order)
and, for the Seller Account route, the
[own-supply sandbox workflow](https://docs.apostra.com/v2/setup/v3/seller-workflows.md#test-your-own-supply).

A buyer account needs its company identity confirmed first, as for any buyer
(`BUYER_SETUP_REQUIRED` says so).

Only that case is allowed. Everything else stays refused while the hold is on:

* Any other buyer, including a sandbox advertiser in another organization.
* A live advertiser, even one in your own organization.
* A buyer account that a seller sponsors. It is not your own account at your
  storefront.
* An archived Seller Account.
* A product that is not active. Activate it first.
* A Seller Account with any other open readiness blocker, apart from the
  sandbox test and the live advertiser mapping, which a sandbox test never
  needs.

## Rules

* **Send the hold fields alone.** One call is one change a person can confirm.
  `isPaused` together with any other `save_seller` field is refused with
  `VALIDATION_ERROR`, and so is `expectedIsPaused` without `isPaused`.
* **A stale `expectedIsPaused` is refused.** If the stored hold no longer matches,
  the call returns [`CONFLICT`](https://docs.apostra.com/v3/errors) with the reason
  `pause_state_changed_concurrently` and saves nothing. Read the Seller Account
  again, confirm the change still applies, and retry.
* **An archived Seller Account is refused.** An archived Seller Account is
  read-only, so the call fails with `VALIDATION_ERROR` for either value.
* **Setting the hold it already has succeeds and changes nothing.** The result
  reports `unchanged`.
* **The `write` role is required**, the same role `save_seller` needs for every
  other change.

Each change that flips the hold is recorded in the audit log, and buyers see it
within seconds.


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