POST /v1/scheduled-posts/:scheduledPostId/reschedule

POST/v1/scheduled-posts/:scheduledPostId/reschedule

Phase 1stable

Auth: Bearer
Scope: publish:write

Move a queued post to a different time. Only posts in status: queued are reschedulable — once a post is publishing or terminal, reschedule returns 409 CONFLICT.

Captions and targets are immutable after scheduling. To change those, cancel and re-schedule from the container.

Path

scheduledPostId
stringrequired
Id returned by schedule or publish.

Body

scheduledFor
string (ISO-8601)required
New publish time. Must be ≥ 30 seconds in the future.

Example request

curl -X POST https://api.layers.com/v1/scheduled-posts/sp_01HXZN4K5M6P7QRS8TUV9WXYZA/reschedule \
  -H "Authorization: Bearer lp_live_01HX9Y6K7EJ4T2_4QZpN..." \
  -H "Content-Type: application/json" \
  -d '{ "scheduledFor": "2026-04-19T18:00:00Z" }'

const post = await layers.publishing.reschedule({
  id: "sp_01HXZN4K5M6P7QRS8TUV9WXYZA",
  scheduledFor: "2026-04-19T18:00:00Z",
});

post = layers.publishing.reschedule(
    id="sp_01HXZN4K5M6P7QRS8TUV9WXYZA",
    scheduled_for="2026-04-19T18:00:00Z",
)

Response

200Rescheduled

{
  "id": "sp_01HXZN4K5M6P7QRS8TUV9WXYZA",
  "status": "queued",
  "scheduledFor": "2026-04-19T18:00:00Z",
  "updatedAt": "2026-04-18T19:21:08Z"
}

Errors

Status	Code	When
422	`VALIDATION`	`scheduledFor` in the past or < 30 seconds from now.
401	`UNAUTHENTICATED`	Missing or invalid key.
403	`FORBIDDEN_SCOPE`	Key lacks `publish:write`.
404	`NOT_FOUND`	Post not in your organization.
409	`CONFLICT`	Post is `publishing` or terminal — not reschedulable.

POST /v1/scheduled-posts/:scheduledPostId/reschedule

Example request

Response

Errors

See also

On this page