Skip to content

reschedule_post

Changes only when a post fires, keeping its copy and target profiles. A failed or draft post is re-armed by this and will go out at the new slot — profiles that already received it are not sent to again. Published posts, and posts currently publishing, cannot be moved.

On this page
  1. Parameters
  2. Example request
  3. Response
Category
Publishing
REST
POST/api/tools/reschedule_post

Parameters

id
stringrequired
ObjectId of the post to move.
scheduleDate
stringrequired
YYYY-MM-DD.
scheduleTime
stringrequired
HH:MM, 24-hour.
timezone
stringoptional
IANA zone for the new slot. Omit to keep the zone the post was scheduled in.
workspaceId
stringoptional
Workspace to act on, from list_workspaces. Omit to use the default workspace on the key.

Example request

curl -X POST "https://api.postmcpai.com/api/tools/reschedule_post" \
  -H "Content-Type: application/json" \
  -H "x-api-key: $POSTMCPAI_API_KEY" \
  -d '{
    "id": "66a50c89e4b019a2b72f",
    "scheduleDate": "2026-08-05",
    "scheduleTime": "09:00"
  }'

Response

The moved post, plus from — the slot it left, so a UI can undo the move.

200 · application/json
{
  "message": "Post rescheduled",
  "post": {
    "id": "66a50c89e4b019a2b72f",
    "scheduleDate": "2026-08-05",
    "scheduleTime": "09:00",
    "status": "scheduled"
  },
  "from": {
    "scheduleDate": "2026-08-02",
    "scheduleTime": "10:00",
    "timezone": "Asia/Kolkata"
  }
}