Update release id
PUT /public/v1/posts/{id}/release-idTells Sharek which item on the platform a post became. Its one real use is repairing a
post whose releaseId came back as missing, so that
post analytics can start working for it.
Also available as sharek posts:connect (CLI); the MCP
server has no tool for it.
Path parameters
Section titled “Path parameters”| Parameter | Required | Description |
|---|---|---|
id |
Yes | The post id. |
| Field | Required | Description |
|---|---|---|
releaseId |
Yes | The platform’s id for the published item, usually taken from missing content. |
Request
Section titled “Request”curl -X PUT https://dash.sharek.app/api/public/v1/posts/post-id/release-id \ -H "Authorization: your-api-key" \ -H "Content-Type: application/json" \ -d '{ "releaseId": "platform-item-id" }'Response
Section titled “Response”The updated post row, without batchId.
- Only a post whose
releaseIdismissingcan be updated. Any other post fails, whether it already has a real id (one you set here included) or has not published yet, so a value cannot be corrected through this operation once it is set. - This does not publish anything or change the post’s state. It records the link between
the Sharek post and the platform item and, when the channel can build one from the id,
fills in the post’s
releaseURLtoo.