Operational status

Postifys Status

Use the live health endpoint for current API process status. Successful publishes still depend on Meta, Google, Pinterest, LinkedIn, and TikTok availability plus each connected account’s permissions.

Open live /health Changelog

Reviewed: 24 July 2026

Live check

API health endpoint

Check JSON at /health

GET https://postifys.com/health returns a small JSON payload used for monitoring. A healthy response means the Postifys web API process is up - not that every social network accepted your last post.

Open /health
Components

What status covers

Postifys API

Live check

Core authenticated publishing API and public marketing site. Verify with /health.

Dashboard & Post History

Account required

After login, Post History shows platform acceptances, delays, and failure reasons for your jobs.

Social platforms

External

Facebook, Instagram, YouTube, Pinterest, LinkedIn, and TikTok can degrade independently. Postifys cannot override their outages or policy rejects.

n8n community node

Depends on your n8n host

The node talks to Postifys over the API. If your n8n instance is down, workflows pause even when Postifys is healthy.

TikTok note: current production delivery uploads eligible videos to the creator inbox. A successful Postifys upload does not mean the video is already public until the creator completes publishing in TikTok. See TikTok integration.

When something fails

Suggested checks

  1. Open /health and confirm the API reports healthy.
  2. In Post History, read the platform error for the specific destination account.
  3. Confirm the connected account is still authorized and has the required permissions.
  4. If the failure is platform-side (media rules, token revoke, provider outage), fix the asset or reconnect and retry.
  5. Still stuck? Email info@postifys.com with the history ID if available.

Need product context too?

See recent public changes on the changelog, or review security and pricing while you wait on a platform recovery.

Changelog Security