Unarchive Send Plan
POST/api/send-plans/:sendPlan/unarchive
Bring an archived plan back to the active list. Archiving overwrote the plan's status, so it is rebuilt: a plan that never finished calculating comes back failed; a working plan comes back ready (the current plan on the Plan tab) only when no other working plan is ready or was calculated after it, otherwise it comes back superseded; every other plan comes back ready. Holds released when the plan was archived are not placed again.
send-plans:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: a Personal Access Token in the Authorization header with the send-plans:write scope. The token's user also needs permission to edit the send planner.
No request body. Returns 422 when the plan is not archived.
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.