Skip to content

Find missing content

GET /public/v1/posts/{id}/missing

Some 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.

Parameter Required Description
id Yes The post id.
Terminal window
curl -H "Authorization: your-api-key" \
https://dash.sharek.app/api/public/v1/posts/post-id/missing
[
{ "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.

[] 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”.

  1. Post analytics answers {"missing": true}.
  2. Call this operation to list candidates.
  3. Identify yours and call update release id with its id.
  4. 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.