Resolve Send Plan Line
POST/api/send-plans/:sendPlan/lines/:line/resolve
Record how an exception on a line was handled, for the send-run checklist. A resolution of skip also marks the line skipped so it is not drafted; any other value (for example accept, expedite, build) is stored as given. Send null to undo a resolution.
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 edit the send planner.
Body fields:
- resolution (string or null, required key, max 32): null clears the resolution.
Returns 404 when the line is not on this plan, and 422 when the plan is not ready.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
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.