Start free

Reliable publishing

Know a post went out, and know early when one will not.

PostBoost checks posts before they go out, warns you before an account disconnects and shows exactly why a post failed, so you can fix it and retry.

Free plan, no credit card. Paid plans include a 14-day free trial.

PostBoost connection health: every account healthy except one LinkedIn Page that needs a reconnect within days

What you get

Webhooks when something changes

Get a webhook when a post publishes or fails, or when an account disconnects or is about to expire.
PostBoost webhook deliveries: every post.published event sent to the team's CRM, with the response to each call

Connection health

One page shows admins which accounts are failing or about to expire.

Warnings before a token expires

Email 7, 3 and 1 days before an account's sign-in expires on Threads, LinkedIn, TikTok, Pinterest and Instagram accounts connected without Facebook.

A clear reason for every failure

The Failed tab shows which account failed and why. Retry that account once the cause is fixed.

Checks before posting

The pre-publish checker looks at the posts due in the next 24 hours (up to a week if you set it) and proposes holding or fixing one before it fails.

No double posts

Posts from the API or an agent are refused if a post with the same text was created for the same account in the last 24 hours, and a daily cap per account stops a runaway script.

Everything in Reliable publishing

How it works

  1. Connect accounts

    Each one shows up on the connection health page.

  2. Let the checks run

    Expiry emails and the pre-publish checker run on their own.

  3. Fix and retry

    Reconnect the account or edit the post, then retry.

Do it from the dashboard, your agent or your code

Dashboard

Admins find connection health under Tools, Insights. Failed posts are on the Failed tab of the posts list.

Ask your agent

“Check next week's scheduled posts and tell me which accounts need reconnecting.”

text MCP tool 
get-account-health, validate-post, retry-failed-post

API

bash 
curl https://postboost.co/app/api/{workspaceUuid}/account-health \
  -H "Authorization: Bearer YOUR_API_TOKEN"
API reference: getAccountHealth

Reliable publishing in one paragraph

PostBoost watches the parts of publishing that usually break. A connection health page lists failing and expiring accounts, emails warn 7, 3 and 1 days before a token expires, and the Failed tab shows why a post failed so one account can be retried. A built-in pre-publish checker reviews the posts due in the next 24 hours, and posts sent through the API or an agent are checked for duplicates and daily caps. Webhooks report published and failed posts and disconnected accounts.

text 
health: GET /account-health
validate: POST /posts/validate
retry: retry-failed-post
guardrails: duplicate 24 h (409), daily caps per account (429), network rules (422), each with a code
webhooks: post.published, post.publishing_failed, account.disconnected, account.token_expiring
docs: https://postboost.co/docs/connection-health/ , https://postboost.co/docs/webhooks/

Questions

How do I know a post was published?

Its status changes to Published in the calendar and posts list, and you can get a post.published webhook.

What happens when an account disconnects?

The account shows a reconnect notice, admins get an email, and the connection health page lists it. Reconnect it and retry the failed posts.

Can PostBoost warn me before a sign-in expires?

Yes, for Threads, LinkedIn, TikTok, Pinterest and Instagram accounts connected without Facebook: an email 7, 3 and 1 days before, plus a webhook if you use one.

Does the checker change my posts?

No. It proposes a fix and nothing changes until someone approves it.

Related

Schedule it and stop checking whether it went out.

Free plan, no credit card.