Your posts.
Your next move.

Manage content before and after publishing

• Drafts and approvals: prepare and review the content before it goes live.
• Scheduled posts: edit or remove the scheduled post before publishing starts. Check its latest status first.
• Published posts: manage each live copy separately. Editing a draft or deleting from Postly does not update an already-published copy.
• Recurring posts and automations: pause future publishing separately when recovering an accidental post.
• Media library: removing a source file is not a way to delete an already-published post. Keep the file while any scheduled post still needs it.

Use the Content Format Guide before publishing, then the platform results below to manage removal.

Format counts are not deletion limits

A ten-image publishing allowance does not mean ten separate posts were created or deleted. A Facebook Multi-image Feed Post, a Facebook Linked Carousel with individual card URLs, and an Instagram Image Carousel are different formats. Reels and Stories are separate live copies for each published file.

Postly’s Delete workflow works on saved published copies; it is not an editor for removing one slide from a carousel or one photo from a feed post. Review every copy in the results, especially when you selected Feed, Reels and Stories together. For changes within a published post, use the platform’s own editing controls where available.

See the Content Format Guide for attachment counts and publishing requirements.

Public API and MCP

DELETE /posts/{postId} and postly_delete_post (also exposed as postly.delete_post) are Delete from Postly operations for every platform. They do not call the provider to delete live content. The ID must be the Postly post ID, not a Facebook post ID, Instagram media ID, or other provider ID.

There is currently no public API or MCP live-deletion action and no Postly action that accepts only a provider ID after the post in Postly has been removed. Preserve IDs and URLs before deleting. If the post is already gone, use the platform directly; contact support with those references if you need help identifying the content, without assuming the post can be restored.

Read the result before closing the incident

Results are grouped by post. Each group shows Postly — Deleted, Postly — Kept, or an outcome that needs attention, followed by the result for each platform. Multiple live copies have their own details. Retry keeps completed removals and attempts unresolved copies again.

For example, if Facebook and LinkedIn are deleted but Instagram is unavailable, the results show Facebook: Deleted, LinkedIn: Deleted, Instagram: Not available, and Postly: Kept. Delete the Instagram post directly, verify it is gone, then use Delete from Postly if you want to remove the remaining post from Postly.

• Deleted / already deleted: the destination removal is resolved. Check the live content when the incident is sensitive.
• Removed from live site: WordPress.com may retain the post in Trash; self-hosted deletion is permanent.
• Unpublished: DEV content was moved to drafts and still exists in DEV.
• Unsupported: manual action is required where the platform allows it. Repeated retries or reconnecting will not add support.
• Connection or permission problem: restore the connection/access and retry while keeping the post in Postly.
• Rate limit or temporary failure: wait and retry; do not recreate or republish the content.
• Not found or unconfirmed: do not assume deletion. Check native access and the live URL. Keep the post in Postly until you resolve the uncertainty.

The dashboard results dialog is the deletion report. A publishing email, Slack notification, Discord notification, or generic Delete from Postly success does not establish that live content was removed.

Agency recovery workflow

1. Before onboarding a client, obtain appropriate delegated access for native Facebook/Instagram operations and agree who can remove accidental posts. Avoid relying on shared passwords.
2. Use drafts and approvals for client publishing. Test publish-and-remove on your own accounts for each destination and format you plan to use.
3. When an incident occurs, pause affected recurring schedules or automations, capture the Postly ID, delivery IDs, live URLs, and the time, and keep the post in Postly.
4. Use Delete on Platforms for supported destinations. Delete unsupported content directly with authorized platform access.
5. Verify each destination independently, including all thread segments and media copies. Record unresolved destinations and assign an operator to them.
6. Only after verification, remove the post in Postly if desired. For content that cannot be recalled, use the appropriate correction or incident-response process.

Official platform references

Reviewed September 30, 2026. The table describes what you can do through Postly. A platform’s wider API capabilities do not automatically mean the feature is available in Postly. Platform rules determine which live actions can succeed; the dashboard reports the outcome for each published copy.

• Facebook Page posts and videos
• Instagram media
• LinkedIn posts
• X posts and Threads posts
• Bluesky post deletion
• YouTube videos, Google Business Profile posts, and Pinterest API
• Telegram messages and Discord messages
• WordPress, WordPress.com, Ghost, DEV, and Blogger
• TikTok publishing, Hashnode API, and WhatsApp Cloud API