Retry Failed Send Plan Drafts
POST/api/send-plans/:sendPlan/drafts/retry
Queue failed draft groups of a plan again. Returns 202 with the drafts being retried.
send-plans:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Bearer Personal Access Token with the send-plans:write scope. The token's user also needs permission to create send planner drafts.
Body fields (all optional):
- draft_id (integer): retry only this failed group. Omit to retry every failed group of the plan.
- hold (boolean): false drafts without holding source stock; omit to hold as the failed group did.
For a send run, every network with units must be approved at its current quantity first (422 with an approvals error otherwise).
Returns 422 when there are no failed drafts.
Request
Responses
- 202
- 401
- 403
- 404
- 422
- 429
Accepted
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.