{"_id":"588a7444def03f0f000b5c48","user":{"_id":"5638f69b22afbc0d001f23c1","username":"","name":"Yammer Platform DL"},"__v":0,"project":"545137a814af501a00b50cf9","initVersion":{"_id":"545137a814af501a00b50cfc","version":"1.0"},"createdAt":"2017-01-26T22:12:20.520Z","changelog":[],"body":"In 2016, Yammer announced an upcoming feature – the ability for users to edit messages after posting. Although it's been a [complex technical challenge](https://medium.com/we-are-yammer/why-is-editing-messages-so-complex-99a05fcaf78e#.5ei4w25j7), we expect the feature to launch this spring.   \nAs developers, you may be wondering – *how will this impact Yammer's Developer Platform?* After speaking with the project team, we have early information to share: \n\n**Yammer Embed – will include editing functionality** \nPopular for SharePoint and intranet sites, the embed feed enables users to view, post, and reply to Yammer messages.  After the launch of the new editing feature, Yammer users will be able to edit messages from within an embed feed. Also, there will be a visual indicator when a message has been edited.  \n\n**Data Export API – will include message versions** \nThere is a new MessageVersions.csv file that will contain all the versions of messages. The existing Messages.csv file will include only the most recent version of each message – unless the latest version was created after the export date range. Message ID will continue to be unique and won't change with edits.  The [online documentation](http://developer.yammer.com/v1.0/docs/data-export-api) has been updated.  \n\n**REST API –  no changes** \nThe endpoints will continue to get the most recent version of each message. The data will not include version history or the edit flag. There will not be endpoints for making edits to messages.   \n\nYammer's developer documentation will be updated in parallel with the feature launch. We want to give you information as soon as it's available, so keep an eye on this site's blog. If you have any questions, please post to the [Microsoft Tech Community](https://techcommunity.microsoft.com/t5/Yammer-Developer/bd-p/YammerDev).","slug":"edit-posts-whats-changing-whats-staying-the-same","title":"Edit Posts – What's Changing & What's Staying the Same"}

Edit Posts – What's Changing & What's Staying the Same


In 2016, Yammer announced an upcoming feature – the ability for users to edit messages after posting. Although it's been a [complex technical challenge](https://medium.com/we-are-yammer/why-is-editing-messages-so-complex-99a05fcaf78e#.5ei4w25j7), we expect the feature to launch this spring. As developers, you may be wondering – *how will this impact Yammer's Developer Platform?* After speaking with the project team, we have early information to share: **Yammer Embed – will include editing functionality** Popular for SharePoint and intranet sites, the embed feed enables users to view, post, and reply to Yammer messages. After the launch of the new editing feature, Yammer users will be able to edit messages from within an embed feed. Also, there will be a visual indicator when a message has been edited. **Data Export API – will include message versions** There is a new MessageVersions.csv file that will contain all the versions of messages. The existing Messages.csv file will include only the most recent version of each message – unless the latest version was created after the export date range. Message ID will continue to be unique and won't change with edits. The [online documentation](http://developer.yammer.com/v1.0/docs/data-export-api) has been updated. **REST API – no changes** The endpoints will continue to get the most recent version of each message. The data will not include version history or the edit flag. There will not be endpoints for making edits to messages. Yammer's developer documentation will be updated in parallel with the feature launch. We want to give you information as soon as it's available, so keep an eye on this site's blog. If you have any questions, please post to the [Microsoft Tech Community](https://techcommunity.microsoft.com/t5/Yammer-Developer/bd-p/YammerDev).