{"_id":"5b32ddee98cb500003e4abf4","project":"545137a814af501a00b50cf9","initVersion":{"_id":"545137a814af501a00b50cfc","version":"1.0"},"user":{"_id":"5b32dd3165bcff00038ea13e","username":"","name":"Tamanna Kottwani"},"__v":0,"createdAt":"2018-06-27T00:44:30.141Z","changelog":[],"body":"This is regarding the recent change made to Open Graph Actions and activity stories. We had a message center post earlier announcing our activity ticker deprecation that was deployed in May 2018.  \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**1) If I am a developer what do I need to do with this new change? **\nNo. 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.  \nYou might chose to no longer send activity stories.  \n\n**2) Are there any other use cases for this end-point? **\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","slug":"open-graph-actions-activity-stories","title":"Open Graph Actions & Activity stories"}

Open Graph Actions & Activity stories


This is regarding the recent change made to Open Graph Actions and activity stories. We had a message center post earlier announcing our activity ticker deprecation that was deployed in May 2018. 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) If I am a developer what do I need to do with this new change? ** No. 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