Skip one queued send

Skips one queued send: the row is marked skipped and the contact's sequence ADVANCES to its next step, with the following step's wait measured from this row's scheduled time. That is what separates skip from decline, which stops the contact's sequence outright. Only a row still waiting to go out can be skipped (scheduled, approval_required or an action-required row); skipping an already skipped row succeeds again and changes nothing. Only sends belonging to campaigns you own can be skipped; anything else answers 404. 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:

• 404 SCHEDULED_SEND_NOT_FOUND — No queued send with this id exists, or its campaign is outside your reach.
• 409 SCHEDULED_SEND_NOT_SKIPPABLE — The send is already settled (sent, stopped, overwritten, replied or failed) and cannot be skipped.
• 422 VALIDATION_FAILED — sendId is not a 24-character hex id.
• 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.