Browse the docs
Developers / Docs / Posting
Reschedule post
Moves a scheduled post to a new time (up to 180 days ahead). Posts that have started publishing cannot move.
Paste it into any AI assistant. The shortcuts open with the prompt typed in; nothing is sent until you press enter.
At a glance
- REST
PATCH https://api.clippie.ai/v1/social/posts/:id
- MCP tool
reschedule_post
- Scope
publish
- Cost
- Spends nothing. Needs the
publishscope and a paid plan, and posts under the user's name: confirm the details with them first.
- Spends nothing. Needs the
Parameters
id- In:
- path
- Type:
- string
- Required:
- Yes
- Description:
- The post id from post_video or list_posts. 1-64 chars.
scheduledFor- In:
- body
- Type:
- string
- Required:
- Yes
- Description:
- The new time (ISO 8601 with a time zone).
Example
curl
curl https://api.clippie.ai/v1/social/posts/ID \
-H "Authorization: Bearer $CLIPPIE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"scheduledFor": "SCHEDULED_FOR"
}'reschedule-post.mjs
const auth = { Authorization: `Bearer ${process.env.CLIPPIE_API_KEY}` };
const res = await fetch('https://api.clippie.ai/v1/social/posts/ID', {
method: 'POST',
headers: { ...auth, 'Content-Type': 'application/json' },
body: JSON.stringify({
"scheduledFor": "SCHEDULED_FOR"
}),
});
if (!res.ok) throw new Error((await res.json()).error.message);
console.log(await res.json());Response
200 with JSON. The full response schema is in the OpenAPI spec.
From an MCP client
Your AI calls reschedule_post with the same fields as JSON arguments. See MCP server to connect one.
tools/call
{
"name": "reschedule_post",
"arguments": {
"id": "ID",
"scheduledFor": "SCHEDULED_FOR"
}
}