Posts

Preview or atomically create a scheduled calendar

Validate 1 to 200 scheduled posts as a batch. Preview with dryRun=true, then apply with the returned snapshot and a unique idempotencyKey. Either every post and the receipt are stored or none are. A cadence may assign UTC instants from startAt and everyMinutes; omit it to give each post its own scheduledAt. Credits are charged when posts publish, not when the calendar is created. Timer arming is best-effort, with the due-post runner as a backstop.

post/v1/posts/calendar

Request

  • Base URL: https://api.postlake.dev
  • URL: https://api.postlake.dev/v1/posts/calendar
  • Auth: bearerAuth (a scheme the document does not define)

Request body

dryRunboolean required
snapshotstring

Required for apply; return value from preview.

idempotencyKeystring

Required for apply; 8 to 128 letters, digits, underscores or hyphens.

Response

Preview with exact UTC slots and snapshot.

dryRunboolean
snapshotstring
matchedinteger
resultsobject[]

Changes

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