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.
blocked after you resume. See
Seller readiness.
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
SendisPaused alone. true holds new business and false resumes it.
expectedIsPaused is the hold you last read. Send it so a change someone else
made after your read is not overwritten.
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 withsave_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
and, for the Seller Account route, the
own-supply sandbox workflow.
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.
isPausedtogether with any othersave_sellerfield is refused withVALIDATION_ERROR, and so isexpectedIsPausedwithoutisPaused. - A stale
expectedIsPausedis refused. If the stored hold no longer matches, the call returnsCONFLICTwith the reasonpause_state_changed_concurrentlyand 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_ERRORfor either value. - Setting the hold it already has succeeds and changes nothing. The result
reports
unchanged. - The
writerole is required, the same rolesave_sellerneeds for every other change.