Skip to main content
Deprecated. This page documents the v2 buyer API, which is closed to new API clients and switches off on 1 December 2026. Use V3 instead: see Move a v2 buyer REST integration to V3. The conversion endpoint, Log event, stays open.
POST /api/v2/buyer/campaign-suggestion-sets/:campaignSuggestionSetId/reject Declines the entire set. Nothing moves, and no member media buy is changed. Rejection is all-or-nothing for the same reason approval is — the members are sides of one transfer. A rejection is not a permanent veto of the campaign. The optimizer will run again, and a later run produces a fresh set for the same campaign. Rejecting is how you decline this recommendation.

Request

Parameters

The body is optional — POST with no body rejects without a reason.

Response

Errors

A reason is worth sending. It is stored with the decision, so it explains later why a run was declined — to your team, and to anyone reviewing how the campaign has been optimized over time.