---
title: "Call the getScheduledPosts MCP tool"
method: POST
path: "/api/v1/actions/getScheduledPosts"
tags: ["Actions"]
---

# Call the getScheduledPosts MCP tool

`POST /api/v1/actions/getScheduledPosts`

## Request

- Base URL: `https://app.reachium.io`
- URL: `https://app.reachium.io/api/v1/actions/getScheduledPosts`
- Auth: HTTP bearer

Read back the publishing calendar: every scheduled (and mid-publish) post in a date window, optionally for one account, ordered by publish time, with the account name, the linked document, and collision flags: two posts from the same account under 4h apart, two posts delivering the same document on one day, a post stuck in publishing, a scheduled post with no publish time, a lead-magnet hook with no campaign, or whose campaign is not active. Undated scheduled/publishing rows are ALWAYS included (they are invisible to every other read). Call this before bulk-scheduling a week and again after, to verify what you set. Defaults: from = now, to = 30 days later. Pass include_approved:true to also see approved posts that still carry a date.

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.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `account_id` string, uuid: Only this LinkedIn account (from getLinkedInAccounts).
  - `from` string: ISO-8601 start of the window (UTC). Defaults to now.
  - `to` string: ISO-8601 end of the window (UTC). Defaults to from + 30 days; at most 120 days after from.
  - `include_approved` boolean: Also list approved posts that carry a scheduled_for (a stale date that unschedulePost can clear).
  - `limit` integer: Max dated posts to return (default 100).

## Response `200`

The result of calling this tool.

- object
  - `data` unknown, required
  - `error` unknown, required

## Other responses

- `400`: The request body was not a JSON object (code invalid_request), or Idempotency-Key is malformed (code invalid_idempotency_key).
- `401`: Missing or invalid API key. Send `Authorization: Bearer rmcp_...` (code unauthorized).
- `403`: This tool is out of the key’s granted scope (code insufficient_scope).
- `409`: This Idempotency-Key has an unresolved in-flight or ambiguous result (code request_in_flight). Reconcile before using a new key.
- `422`: This Idempotency-Key was already used with a different request body (code idempotency_key_reuse).
- `429`: Rate limited: shared `mcp:ip:{ip}` (600/60s) or `mcp:key:{keyId}` (120/60s) bucket, the SAME buckets the MCP endpoint uses (code rate_limited).
- `500`: Unhandled server error (code internal_error).

---

[API](https://skmtc.dev/reachium/apis/reachium-api.md) · [All operations](https://skmtc.dev/reachium/apis/reachium-api/llms.txt) · [OpenAPI document](https://skmtc.dev/reachium/apis/reachium-api/revisions/30c16b30b499?raw)