Scheduling

Spread many drafts across your preset posting times

The bulk scheduler. Resolves a group (or an explicit account list) to targets, then assigns drafts to your preset wall-clock times, minPerDay posts per day, walking forward from startDate and skipping any slot less than five minutes away. Every post goes to every resolved account. Set dryRun to true to see the plan without creating any timers. Always do this first. At most 50 posts are scheduled per call; the rest come back in skipped with a reason, so call again to continue. Targets are capped at 10 accounts.

post/schedule

Request

  • Base URL: https://www.juzpost.com/api/cli/v1
  • URL: https://www.juzpost.com/api/cli/v1/schedule
  • Auth: HTTP bearer

Request body

minPerDayinteger required

How many posts to place per day. Must not exceed the number of available time slots, or the call fails with 422. Add more times or lower this number.

groupstring

Name of the channel group whose accounts should receive every post, matched exactly as returned by GET /groups. Unknown names return 404.

socialAccountIdsstring[]

Explicit accounts to receive every post, used instead of group. Duplicates are collapsed. More than 10 distinct accounts is rejected with 422.

postIdsstring[]

The specific drafts to schedule, in the order you want them placed. Omit this to use every draft you have, oldest first, up to 200. Any id that is not one of your drafts is reported in skipped rather than failing the call.

startDatestring date

First calendar day to place posts on, as YYYY-MM-DD in your timezone. Defaults to tomorrow. Slots less than five minutes away are skipped, so a start date in the past simply yields fewer usable slots.

timesstring[]

Wall-clock posting times as HH:MM in your timezone, overriding the your defaults for this call only. Times are sorted ascending and the earliest minPerDay of them are used each day.

dryRunboolean

When true, compute and return the plan without creating any timers. Run this first to confirm the dates look right, then repeat without it.

Response

The plan, plus what was scheduled and what was skipped. Individual entries in scheduled may carry status: failed with an error, so check them.

dryRunboolean

Present and true only when the request set dryRun. Its absence means timers were actually created.

Changes

No recorded changes to this operation across all 1 revision of this API.