{"_id":"5b3f2b73cc4511000331a2ca","project":"545137a814af501a00b50cf9","version":{"_id":"545137a814af501a00b50cfc","project":"545137a814af501a00b50cf9","__v":11,"createdAt":"2014-10-29T18:53:28.525Z","releaseDate":"2014-10-29T18:53:28.525Z","categories":["545137a814af501a00b50cfd","545138eaa66f020800dbab4a","546b9072b47b5d1400109edf","546b9082b47b5d1400109ee0","546b9088b47b5d1400109ee1","546b909462515a14007ebc43","546b90a0b47b5d1400109ee2","546ced235884600e007a92f6","5481008eea7fd40b00cd7c2b","573b9d83ee2b3b220042291f","57be1efa15efc70e006a5f99"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"category":{"_id":"546b9072b47b5d1400109edf","project":"545137a814af501a00b50cf9","version":"545137a814af501a00b50cfc","__v":6,"pages":["546bdfb555639108002b1842","546be31f52812008000414af","546be32e55639108002b184a","546be33c52812008000414b1","546be34a52812008000414b3","546be36255639108002b184c"],"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2014-11-18T18:31:14.459Z","from_sync":false,"order":4,"slug":"open-graph","title":"Open Graph"},"user":"5b32dd3165bcff00038ea13e","githubsync":"","__v":2,"updates":["5b43b62de86bc40003d80c5e","5b47e41e5d47b70003c23d68"],"next":{"pages":[],"description":""},"createdAt":"2018-07-06T08:42:27.615Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":999,"body":"This is regarding the recent change made to 3rd party Open Graph Actions and activity stories. We had a message center post earlier announcing our activity ticker deprecation that was deployed in May 2018. \nDetails for this post are here:\nhttps://techcommunity.microsoft.com/t5/Yammer-Blog/Rationalizing-experiences-in-Yammer-and-Office-365/ba-p/185078\n\nDevelopers of 3rd party applications earlier used activity stories to push out updates that would be shown in the Activity Ticker. As the Ticker is deprecated, these activity stories do not surface anywhere in the product any longer. Hence we have deprecated api/v1/activity.json to reflect this change.  \n\n**FAQs: **\n\n**1) How can developers best respond to this change? **\n\nYou just need to be aware that the endpoint will now return a 410 Gone client error response code that indicates that the access to the target resources is no longer available.  \nYou might chose to no longer send activity stories.  \n\n**2) Are there any other use cases for this end-point? **\n\nWe have found that some third parts apps use this endpoint to update properties for Open Graph Objects (OGOs). Although this endpoint was not designed for this, if you have been doing so, we recommend moving to the new endpoint api/v1/open_graph_objects.json \n\n**3) If we are using this endpoint to update properties for Open Graph Objects (OGOs), how do we move to the new endpoint api/v1/open_graph_objects.json temporarily?**\n\nRefer to the details below:\n\nThe Activity Stories that were passed on earlier were of the below format. If you were using OGAs for \nupdating properties for Open Graph Objects (OGOs), you need to move to the new endpoint api/v1/open_graph_objects.json by now passing on parameters as below\n\n{\n  \"user_client\":{\n    \"id\":10,\n    \"type\":\"AndroidGCMPushDevice\",\n    \"network_id\":99,\n    \"client_id\":\"some-test-client\"\n  },\n  \"template\":\"mark_read\",\n  \"user\":{\n    \"id\":1,\n    \"meta_user_id\":2\n  },\n  \"message_id\":1001,\n  \"thread_id\":1002\n}\n\n**4) What is the new payload if a developer was using OGAs (Open Graph Actions) to update properties for OGOs (Open Graph Objects) ?**\n\napi/v1/activity.json will now return a 410 Gone client error response. \nOld Parameters that were passed for this endpoint were as below:\n\n{\n  \"activity\": {\n    \"actor\": {\"name\": \"Jim Patterson\", \"email\": \"jpatterson:::at:::alpinestyle.com\"},\n    \"action\": \"create\",\n    \"object\": {\n        \"url\": \"https://dox.com/file/abc123.pdf\",\n        \"description\": \"A set of charts showing the ROI of deploying Yammer over time.\",\n        \"video\": {\n            \"width\": 500,\n            \"height\": 400\n        },\n        \"type\": \"file\",\n        \"title\": \"Yammer ROI.pdf\",\n        \"image\": \"https://dox.com/file/abc123.png\"\n  },\n  \"private\": \"false\",\n  \"message\": \"This is the updated version for the conference.\",\n  \"users\": [\n    {\"name\": \"Mary Shamone\", \"email\" : \"mshamone@alpinestyle.com\"},\n    {\"name\": \"Christina Ammerlaan\", \"email\" : \"cammerlaan@alpinestyle.com\"}\n  ]\n  }\n}\n\nNew parameters needed to be passed for the new endpoint (api/v1/open_graph_objects.json) as below: \n\n{\n  \"user_client\":{\n    \"id\":10,\n    \"type\":\"AndroidGCMPushDevice\",\n    \"network_id\":99,\n    \"client_id\":\"some-test-client\"\n  },\n  \"template\":\"mark_read\",\n  \"user\":{\n    \"id\":1,\n    \"meta_user_id\":2\n  },\n  \"message_id\":1001,\n  \"thread_id\":1002\n}\n\nNOTE: We advise not using the api/v1/open_graph_objects.json endpoint to update OGO properties. This has been temporarily been made available as a fix and is not the intended use of the endpoint.","excerpt":"(Change Notification)","slug":"oga-announcement","type":"basic","title":"OGA Announcement"}

OGA Announcement

(Change Notification)

This is regarding the recent change made to 3rd party Open Graph Actions and activity stories. We had a message center post earlier announcing our activity ticker deprecation that was deployed in May 2018. Details for this post are here: https://techcommunity.microsoft.com/t5/Yammer-Blog/Rationalizing-experiences-in-Yammer-and-Office-365/ba-p/185078 Developers of 3rd party applications earlier used activity stories to push out updates that would be shown in the Activity Ticker. As the Ticker is deprecated, these activity stories do not surface anywhere in the product any longer. Hence we have deprecated api/v1/activity.json to reflect this change. **FAQs: ** **1) How can developers best respond to this change? ** You just need to be aware that the endpoint will now return a 410 Gone client error response code that indicates that the access to the target resources is no longer available. You might chose to no longer send activity stories. **2) Are there any other use cases for this end-point? ** We have found that some third parts apps use this endpoint to update properties for Open Graph Objects (OGOs). Although this endpoint was not designed for this, if you have been doing so, we recommend moving to the new endpoint api/v1/open_graph_objects.json **3) If we are using this endpoint to update properties for Open Graph Objects (OGOs), how do we move to the new endpoint api/v1/open_graph_objects.json temporarily?** Refer to the details below: The Activity Stories that were passed on earlier were of the below format. If you were using OGAs for updating properties for Open Graph Objects (OGOs), you need to move to the new endpoint api/v1/open_graph_objects.json by now passing on parameters as below { "user_client":{ "id":10, "type":"AndroidGCMPushDevice", "network_id":99, "client_id":"some-test-client" }, "template":"mark_read", "user":{ "id":1, "meta_user_id":2 }, "message_id":1001, "thread_id":1002 } **4) What is the new payload if a developer was using OGAs (Open Graph Actions) to update properties for OGOs (Open Graph Objects) ?** api/v1/activity.json will now return a 410 Gone client error response. Old Parameters that were passed for this endpoint were as below: { "activity": { "actor": {"name": "Jim Patterson", "email": "jpatterson@alpinestyle.com"}, "action": "create", "object": { "url": "https://dox.com/file/abc123.pdf", "description": "A set of charts showing the ROI of deploying Yammer over time.", "video": { "width": 500, "height": 400 }, "type": "file", "title": "Yammer ROI.pdf", "image": "https://dox.com/file/abc123.png" }, "private": "false", "message": "This is the updated version for the conference.", "users": [ {"name": "Mary Shamone", "email" : "mshamone@alpinestyle.com"}, {"name": "Christina Ammerlaan", "email" : "cammerlaan@alpinestyle.com"} ] } } New parameters needed to be passed for the new endpoint (api/v1/open_graph_objects.json) as below: { "user_client":{ "id":10, "type":"AndroidGCMPushDevice", "network_id":99, "client_id":"some-test-client" }, "template":"mark_read", "user":{ "id":1, "meta_user_id":2 }, "message_id":1001, "thread_id":1002 } NOTE: We advise not using the api/v1/open_graph_objects.json endpoint to update OGO properties. This has been temporarily been made available as a fix and is not the intended use of the endpoint.