Back to Changelog
v2026.07.29

Safer post updates and clearer billing status

Today's release closes a set of silent-failure gaps in post updates and TikTok publishing, and makes API access rules match your billing status:

  • Partial updates no longer wipe your platform settings: Sending a partial update to PATCH /v1/posts/:id (or the update_post MCP tool) that only touches one field of a network's config, like TikTok's disableComment, used to silently erase every other field you'd set for that network, including things like privacy level and post mode. These updates now merge field-by-field within each network's config, so untouched settings are preserved.
  • Unrecognized config fields now trigger a warning: Typos or wrong casing in platform-specific config (like post_mode instead of postMode, or a tiktok field that doesn't exist) were previously stripped silently, sometimes causing a post to land as a draft instead of publishing. Both post creation and updates now warn on unrecognized keys anywhere inside a network's config block, with a suggestion when your key is a close match to a real one.
  • Clearer API errors when a subscription lapses: Requests to the API or MCP server from an organization without an active subscription now return a clear 402 Payment Required response with a link to your billing page, instead of continuing to work indefinitely or failing with confusing errors. Access resumes immediately once your subscription is active again.
  • Faster, more reliable TikTok post lookups: GET /v1/posts/:id now saves the resolved TikTok video ID the first time it's looked up, instead of re-resolving it on every request. Post URLs and future lookups are quicker as a result, with no change in behavior for you.