{"_id":"555f6ca257fe0a0d00c8f502","user":{"_id":"5433099f9a2b451a00ad4531","username":"","name":"Ryan Braastad"},"project":"545137a814af501a00b50cf9","__v":1,"initVersion":{"_id":"545137a814af501a00b50cfc","version":"1.0"},"tags":[],"createdAt":"2015-05-22T17:51:30.482Z","changelog":[{"_id":"5638efdc2fc5520d001a4cfd","update":"","type":"added"}],"body":"Starting from May 22nd, Yammer will rollout a new feature that allows users to add external participants to any thread (private conversations, public and private group messages) in their network.\n\n**In order to support this feature, we are making the following changes to our API:**\n\n1)  References to objects belonging to external participants will be provided in the external_references section of the payload; these references will contain only the subset of attributes that are visible to an external user.\n\n2)  Every object has a network_id attribute which can be used to check whether an object is external or not.\n\n3)  The autocomplete endpoint will return suggestions for external users the current user has already interacted with.\n\n4)  Attaching an open graph object, a topic, or a tag to a message as an external participant is not allowed.\n\n5)  Data export has been updated, it will now include the MessageThread model as well, which has information about the external participants in the thread, plus the files and pages included in those message threads.\n \n[block:api-header]\n{\n  \"type\": \"basic\"\n}\n[/block]\nThe biggest change for you is that when you inspect the payload in search for references, you need to look for references also in the external_references section.\n\nTo get access to the new API format you need to provide the header yammer-capabilities: external-messaging when making requests to the Yammer API. In case you don't pass the header, you will get the old API format but objects belonging to external participants will be filtered out. We will maintain the dual API format until November 18th; afterwards, you will not need to pass the yammer-capabilities header anymore.\n\nIf you are looking for more information about how the feature works you can visit: \n\nhttps://support.office.com/en-ca/article/Add-external-participants-to-your-Yammer-conversations-423653bb-86b2-4eac-9d7e-dca121f7c16c\n\n[block:api-header]\n{\n  \"type\": \"basic\"\n}\n[/block]\nBy The Yammer Platform Team. Posted on May 22, 2015","slug":"external-messaging-developer-update","title":"External Messaging Developer Update"}

External Messaging Developer Update


Starting from May 22nd, Yammer will rollout a new feature that allows users to add external participants to any thread (private conversations, public and private group messages) in their network. **In order to support this feature, we are making the following changes to our API:** 1) References to objects belonging to external participants will be provided in the external_references section of the payload; these references will contain only the subset of attributes that are visible to an external user. 2) Every object has a network_id attribute which can be used to check whether an object is external or not. 3) The autocomplete endpoint will return suggestions for external users the current user has already interacted with. 4) Attaching an open graph object, a topic, or a tag to a message as an external participant is not allowed. 5) Data export has been updated, it will now include the MessageThread model as well, which has information about the external participants in the thread, plus the files and pages included in those message threads. [block:api-header] { "type": "basic" } [/block] The biggest change for you is that when you inspect the payload in search for references, you need to look for references also in the external_references section. To get access to the new API format you need to provide the header yammer-capabilities: external-messaging when making requests to the Yammer API. In case you don't pass the header, you will get the old API format but objects belonging to external participants will be filtered out. We will maintain the dual API format until November 18th; afterwards, you will not need to pass the yammer-capabilities header anymore. If you are looking for more information about how the feature works you can visit: https://support.office.com/en-ca/article/Add-external-participants-to-your-Yammer-conversations-423653bb-86b2-4eac-9d7e-dca121f7c16c [block:api-header] { "type": "basic" } [/block] By The Yammer Platform Team. Posted on May 22, 2015