Skip to main content

Changelog

All notable changes to the PostEverywhere API.

2026-04-12 — scheduled_for rename, strict field validation, scope visibility​

scheduled_for is now the canonical request field for scheduling posts. The old name scheduled_at was a misnomer — it read as a past-tense timestamp (like created_at / updated_at) even though it represented a future moment when the post will publish. scheduled_for makes the intent explicit.

  • scheduled_for is the canonical request field name (was scheduled_at). The response also returns the value under scheduled_for, completing the round-trip.
  • scheduled_at is deprecated but still accepted as an alias. Existing integrations built before 2026-04-12 will continue to work unchanged. New integrations should use scheduled_for.
  • Strict 400 validation for unknown media field names. If you send media, media_id, mediaId, or attachments in a request body, the API now returns 400 invalid_field_name with a helpful did you mean media_ids? hint. The only accepted media field on requests is media_ids (an array of UUID strings).
  • OAuth scope visibility. When a user reconnects a social account and the platform drops scopes from the grant, we now record the drop and alert on the mismatch, so silently-broken integrations surface quickly.
  • Body logging for v1 endpoints. The v1 API now logs sanitized request bodies (with API keys and tokens redacted) for debug visibility, making it much easier to trace bad requests when you email developer support.
  • Round-trip principle. Every top-level field name in a request body also appears in the response with the same name and meaning. You can take a post you got from GET /v1/posts/{id} and POST its fields straight back to clone it — no renaming.

v1.0 — March 2026​

  • Initial public API release
  • 18 endpoints across Accounts, Posts, Media, and AI
  • Support for 8 platforms: Instagram, TikTok, YouTube, LinkedIn, X, Facebook, Threads, Pinterest
  • Bulk scheduling (up to 100 posts per request)
  • AI image generation
  • MCP server integration for Claude Code
  • Node.js SDK

Subscribe to API updates by emailing [email protected].

Resources: