Recover a post's failed destinations

Creates a new draft post for the destinations where a post failed to publish, so you can fix it and send it again. Use it on a post whose status is partial (some destinations went live, some failed) or error (none went live). The draft copies the original content and media and targets only the failed connections. Nothing is published or scheduled: edit the draft if the network rejected the content, then schedule or publish it like any other post. The draft can target only those failed destinations, so adding another connection to it is refused with 409. The live destinations on the original post are never changed. The failed destinations move to the draft and can no longer be retried from the original, so a partial post then shows as active. Calling this again for the same post returns the same draft with 201 instead of creating a second one. If that draft was deleted, the call returns 409 and no new recovery is made. A destination is left on the original when its outcome is uncertain (the network may already have the post), when a retry is already queued, or when its platform is not currently offered. If no destination qualifies, the call returns 422. Series posts, posts that belong to a multi-client post and imported posts can't be recovered here. The API key's user must be active and have access to Social and to the post's client. If recovery isn't available for your workspace, the call returns 404. Send no request body.