Find missing content
GET /public/v1/posts/{id}/missingSome platforms publish successfully but do not tell Sharek which item was created. When
that happens Sharek marks the post’s releaseId as missing, and analytics for it
cannot be fetched, because there is no platform id to ask about.
This operation lists the candidate items on the platform so you can pick the right one, then record it with update release id.
Also available as sharek posts:missing (CLI); the MCP
server has no tool for it.
Path parameters
Section titled “Path parameters”| Parameter | Required | Description |
|---|---|---|
id |
Yes | The post id. |
Request
Section titled “Request”curl -H "Authorization: your-api-key" \ https://dash.sharek.app/api/public/v1/posts/post-id/missingResponse
Section titled “Response”[ { "id": "platform-item-id", "url": "https://platform.example/p/123" }, { "id": "another-item-id", "url": "https://platform.example/p/122" }]Open the URLs, decide which one is your post, and send that id to
update release id.
An empty array is the normal case
Section titled “An empty array is the normal case”[] comes back whenever there is nothing to resolve, which covers several situations
that are not errors:
- The post published normally and already has a real
releaseId. - The post has not published yet.
- The post’s provider does not support this lookup at all. Most do not.
So [] means “nothing for you to do here”, not “something went wrong”.
The full recovery flow
Section titled “The full recovery flow”- Post analytics answers
{"missing": true}. - Call this operation to list candidates.
- Identify yours and call update release id with its id.
- Analytics work from then on.
- Sharek refreshes the channel’s access token first if it has expired. If that refresh
fails, the answer is
[]and the channel needs reconnecting in the app.