Skip to main content
GET
Fetch the latest posts in key scope along with a summary, or read one calendar window of posts by their scheduled time. Use this to track delivery status across supported platforms, including posts scheduled by your OpenClaw agent or automation scripts, or to build a content calendar.
Only posts that include deliveries for accounts owned by the authenticated key scope are returned. Hosted and BYO accounts are both supported, and deliveries for accounts outside scope are filtered out automatically.

Query Parameters

string
Filter by status: draft, pending, scheduled, posted, failed, partial, retry, canceled. When omitted, all statuses are returned.
string
Several statuses, comma-separated (for example scheduled,posted). Use status or statuses, not both.
number
default:"100"
Number of posts to return. Values below 1 are treated as 1; values above 100 are clamped to 100.
number
default:"0"
How many posts to skip, for the next page.
string
Start of a calendar window: ISO 8601 with offset. Only posts scheduled at or after this time. Send it with scheduled_until.
string
End of the calendar window (inclusive), at most 62 days after scheduled_from.
string
Only posts going to these account ids, comma-separated (up to 50). Ids outside the key scope match nothing.
string
default:"created_at"
created_at (newest first) or scheduled_time (earliest scheduled first, for a calendar).
string
ISO timestamp. Only include posts created on or after this time.
string
ISO timestamp. Only include posts created on or before this time.
since and until must be valid ISO 8601 strings. Invalid values return a 400 response with error_code set to invalid_since or invalid_until. A calendar window that is missing an end, reversed, or longer than 62 days returns 400 invalid_scheduled_window.
A week of a content calendar is one request: scheduled_from and scheduled_until around the week, sort=scheduled_time and limit=100.

Response

Returns a summary object with counts and a posts array.
object
Scope-wide counters.
array
List of post objects. Each post may include tiktok and/or pinterest settings when those platform-specific payloads were provided at create/update time, and settings with the stored settings.<provider> objects. media is null for text-only posts. Each entry of accounts.states names the destination’s platform and username.
summary.by_status tracks canonical lifecycle buckets (draft, pending, scheduled, posted, partial, failed). Provider-facing statuses (for example deleted/void) can still appear on individual post/account status fields and are included in summary.total.

Error Responses

  • 400 invalid_since or 400 invalid_until - query params failed ISO parsing
  • 400 invalid_scheduled_window - a calendar window is missing an end, reversed, or longer than 62 days
  • 400 invalid_statuses, 400 invalid_account_ids, 400 invalid_sort, 400 invalid_offset - a filter value is not allowed
  • 401 - authentication failed (missing/invalid/revoked token)
  • 402 subscription_required - active Creator/Professional/Business plan required
  • 403 tier_not_allowed - Scheduler tier cannot use Partner API
  • 500 list_failed - Database query or summary computation failed