Call the scheduleSlot MCP tool
Schedule an existing planned/draft content-plan slot for publishing at its PRESET time (from generatePlan): does NOT recompute the timestamp. This publishes to LinkedIn via the scheduler (a LAUNCH action). Two-step: the FIRST call (no confirm_token) returns a preview and a confirm_token and does NOT schedule. After the user approves, call again with the same post_id plus confirm_token. The preset time is UTC: restate it in the user's local timezone when you relay the preview. Undo before it publishes: unschedulePost.
Called through the Actions bridge: the response is that tool's own result, wrapped as { data: <tool result> } under HTTP 200. Billing, daily-cap, and confirm-step outcomes are embedded INSIDE data, never remapped to an HTTP status (see the templated /api/v1/actions/{toolName} operation above for the full protocol, and x-mcp-actions for this tool's machine-readable scope/cap/confirm_behavior fields). Authentication, request-shape, and optional idempotency-protocol failures still use their documented non-200 statuses.
Request
- Base URL: https://app.reachium.io
- URL: https://app.reachium.io/api/v1/actions/scheduleSlot
- Auth: HTTP bearer
Headers
Optional caller-generated key (8-200 characters: letters, digits, dot, underscore, colon, or hyphen). A final tool result is replayed for the same key and body. An ambiguous result remains 409 under that key; reconcile external state before using a new key. Reuse with a different body returns 422.
Request body
Response
The result of calling this tool.
Changes
No recorded changes to this operation across all 3 revisions of this API.