Decline queued sends awaiting review

Declines queued sends. A declined row moves to stopped, which is TERMINAL for that contact: unlike skip, the sequence does not advance, so no further step is scheduled for the contact in this campaign. Decline reaches both AI drafts awaiting review (approval_required) and ordinary queued rows (scheduled), so it is also how you call off an upcoming send for one contact. Only sends belonging to campaigns you own can be declined. The answer reports every id you passed: declined are the ones that moved, ignored are your sends in a state decline cannot move (already sent, skipped, stopped or overwritten), and notFound are ids that do not exist, are not yours, or belong to a deleted campaign. Rate limit: 30 requests/minute and 1,000/day per token owner, shared by every campaign, scheduled-send, campaign-template and knowledge-hub endpoint.

Errors:

• 422 VALIDATION_FAILED — sendIds is missing, empty, longer than 100, contains a duplicate, or an entry is not a 24-character hex id; param names the field.
• 429 RATE_LIMITED — More than 30 campaign requests in a minute, or 1,000 in a day, for this token owner (the bucket is shared by every /business/campaigns, /business/scheduled-sends, /business/campaign-templates and /business/knowledge-hubs call).
• 500 UNEXPECTED_ERROR — An unhandled failure; the detail stays in our logs and is never returned.

Requires one of the following token scopes: campaigns.