Actions

Call the unschedulePost MCP tool

Cancel a SCHEDULED post before it publishes ("cancel that post", "don't send it"). Plan slots revert to planned and keep their currently set time; ad-hoc posts revert to approved with the time cleared. On an APPROVED post that still carries a stale date, clears that date (status unchanged). Cannot touch already-published posts; failed/stuck posts go through revertPostToDraft. Safe to call: it only ever reduces LinkedIn activity.

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.

post/api/v1/actions/unschedulePost

Request

  • Base URL: https://app.reachium.io
  • URL: https://app.reachium.io/api/v1/actions/unschedulePost
  • Auth: HTTP bearer

Headers

Idempotency-Keystring

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

post_idstring uuid required

The scheduled post to cancel (from getContent or a schedule result).

Response

The result of calling this tool.

dataunknown required
errorunknown required

Changes

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