ZernioInstall

Summary

Update an existing social media post by specifying its Post ID and providing updated content, scheduling details, visibility, platform selections, and optional media or thread items for various supported platforms.

Inputs

• Post ID (required) — The unique identifier of the post to update, obtainable from listing posts or post creation responses.
• Content (required) — The main text content of the post, used across all selected platforms with support for emojis and hashtags.
• Scheduled For — Optional future date/time to schedule the post's publication; leave empty for immediate publishing.
• Timezone — Timezone to use for scheduling, defaults to UTC for accurate cross-timezone scheduling.
• Publish Now — Boolean flag to publish the post immediately, which overrides any scheduled time.
• Is Draft — Boolean flag to save the post as a draft instead of publishing or scheduling it.
• Visibility — Defines who can see the post: public, private (followers/connections only), or unlisted (accessible via direct link but not in feeds).
• Tags — Comma-separated keywords primarily for YouTube search optimization.
• Platforms (required) — Select one or more social media platforms where the post should appear.
• Platform Account Selections — For each selected platform, choose specific accounts for publishing the post (e.g., Twitter/X accounts, Instagram accounts, etc.).
• Media Items — Optional media files to attach, each with type, URL, filename, and MIME type (for documents).
• Platform-Specific Thread or Conversation Items — For platforms like Twitter/X, Threads, Bluesky, specify multiple threaded posts with separate content and media per post.
• TikTok Privacy and Content Settings — Settings specific to TikTok posts including privacy level, comment/duet/stitch permissions, media type, commercial content disclosures, and AI content declaration.

Output shape

a single record representing the updated post's details as returned by the Zernio API.

Ensure all required fields are provided. Multiple platform accounts and thread items must be correctly specified to reflect the post update. The operation may accept batching and proxy configurations via request options.