Skip to main content
Requires CLI 0.2.18 or later. Saved drafts are available to all users. Draft saves use no posting allowance. They never publish or assign a date.
Use the draft UUID and current revision returned by Mallary. The numbers above are examples; read the actual revision before each write. A 409 means you must read again. Supplied lists and platform settings replace their saved values; omitted fields stay unchanged. Use --file changes.json with empty arrays to clear media, comments, or destinations. Create and edit support --message, repeated --platform, --profile-id, repeated --media, --thumbnail, repeated --comment, --post-type, --auto-reply-enabled, or --file. File mode supports the draft API content fields. --expected-revision is required for edits and can be supplied with file mode. Local media files upload to Mallary before saving. A saved draft does not make uploaded media private.

​
Publish or Schedule

Only use these commands when the user asks to publish or schedule the saved post:
Omit the date to publish now. Normal plan, account, content, and platform checks apply. Validation failures leave the draft saved. Repeating the exact revision and schedule returns the original publishing jobs. After an uncertain response, read the draft; a submitted draft includes submission. Do not create a new post as a retry. Draft saves reject schedule fields, webhook URLs, and publishing idempotency keys. List and get use read scope. Save, edit, delete, and submit use publish scope. For reads, deletes, and submissions, --profile-id optionally verifies the source profile. For edits, it changes the saved profile. A draft uses one connection profile.
Last modified on October 9, 2026