List posts
GET /public/v1/postsReturns the posts on your calendar between two dates. This is the read side of the calendar: use it to sync what is scheduled, or to find a post id you did not keep.
Doing this in the app? See the calendar. Also available as
sharek posts:list (CLI) and
postsListTool (MCP).
Query parameters
Section titled “Query parameters”| Parameter | Required | Description |
|---|---|---|
startDate |
Yes | ISO 8601 date and time. Start of the window. |
endDate |
Yes | ISO 8601 date and time. End of the window. |
customer |
No | A brand id from list brands. Limits results to that brand’s channels. The app calls them brands; the API calls them groups in its path and customer in its fields. |
Both dates are required, and both are UTC. A missing or malformed date is a 400 with
the field-validation shape.
Request
Section titled “Request”curl -H "Authorization: your-api-key" \ "https://dash.sharek.app/api/public/v1/posts?startDate=2026-09-01T00:00:00.000Z&endDate=2026-09-30T23:59:59.000Z"Response
Section titled “Response”{ "posts": [ { "id": "post-id", "content": "Hello from the Sharek API", "publishDate": "2026-09-01T10:00:00.000Z", "releaseURL": null, "releaseId": null, "state": "QUEUE", "error": null, "intervalInDays": null, "group": "group-id", "creationMethod": "API", "settings": "{\"who_can_reply_post\":\"everyone\",\"__type\":\"x\"}", "tags": [ { "tag": { "id": "tag-id", "name": "Launch", "color": "#942828", "orgId": "org-id", "deletedAt": null, "createdAt": "2026-08-20T09:00:00.000Z", "updatedAt": "2026-08-20T09:00:00.000Z" } } ], "integration": { "id": "channel-id", "providerIdentifier": "x", "name": "Sharek on X", "picture": "https://example.com/avatar.png" } } ]}Unlike list channels, this one wraps its array in an object.
| Field | Description |
|---|---|
id |
The post id, for every other post operation. |
content |
The post text. |
publishDate |
When it is scheduled for, or when it went out. |
releaseURL |
The link to the published post, once there is one. |
releaseId |
The platform’s own id for the published item. The literal string missing means Sharek could not match it, which is what missing content is for. |
state |
QUEUE scheduled, DRAFT a draft, PUBLISHED already out, ERROR it failed. |
error |
Why the platform refused the post, when it gave a readable reason. Otherwise null. |
intervalInDays |
Set when the post repeats. null for a one-off. |
group |
The group this post shares with the replies in its thread. Each channel’s post has its own, so deleting by group removes this post and its replies only. |
creationMethod |
How it was created, for example API or CLI. |
settings |
The channel settings the post was saved with, as a JSON string. Parse it before reading the values. |
tags |
The post’s tags, each one wrapped in a tag object. |
integration |
The channel it belongs to. |
Only top-level posts are returned. The replies in a thread are children of their post and do not appear as separate entries.
- Not paginated. Everything in the window comes back in one response, so keep windows reasonable rather than asking for a year at once.
- Recurring posts are expanded inside the window. A repeating post comes back once
for each occurrence that falls between
startDateandendDate. Each entry carries that occurrence’s time inpublishDate, with the series’ original time preserved inactualDate. A series that started beforestartDateappears only through its occurrences inside the window. - One post per channel. A single create call across three channels
shows up here as three posts, each with its own
idandgroup. - Posts on deleted channels are excluded.