Microsoft Technical Bulletins

The latest updates for all the Microsoft Products you use every day.

Written by QuixTec LLC

My goal is to help your business by integrating processes that automate mundane tasks and simplify complex ones without breaking budgets.

Categories: Yammer

December 14, 2021

Blog Home

(Updated) Yammer Public Links API Changes

From Microsoft Corporation
Technical Bulletin: MC283912 · Published Sep 9, 2021 · Last updated Sep 27, 2021

ACTION REQUIRED BY MAR 1, 2022

Message Summary

Updated September 27, 2021: We have updated this message with additional details for clarity. Thank you for your feedback.

We’re making some changes to public OGOs (Open Graph Objects) over the next two quarters. The effected APIs are:

  • GET api/v1/open_graph_objects?url=https://
  • GET /messages/open_group_objects/:id.json

Key points

  • Timing: March 1, 2022
  • Control type: admin control
  • Action: review and assess

How will this affect your organization?

Phase 1 (November 1st, 2021) – No breaking change to GET api/v1/open_graph_objects?url=https://

After November 1st, we will add a list consisting of a single OGO (which is the same OGO currently being returned by the API) to the response of GET api/v1/open_graph_objects?url=https:// – this is unlikely to affect your usage of this API, but we still recommending checking how you are consuming the API before the change happens.

Here is an example of what the response of the API will look like:

{

“id”: 12345,

…,

“ogos”: {

“id”: 12345,

….

}

}

Phase 2 (February 1st, 2022) – No breaking change to GET api/v1/open_graph_objects?url=https://

Then on February 1st, 2022, all public Open Graph Objects (OGOs) will be associated with only the message it is attached to. These links, and the messages associated with them, are only visible to users who have access to the conversations the Open Graph Objects were a part of.

Previously, there was only one OGO in each Yammer Network per absolute URL. Now there will be multiple OGOs that exist because this new change will create one OGO per message the URL is attached to.

GET api/v1/open_graph_objects?url=https:// – will return, in the existing field, any OGO id from the list. In the new field, it will return the full list of OGOs for that url.

Phase 3 (March 1st, 2022) – Breaking change to GET api/v1/open_graph_objects?url=https://

Following this, on or after March 1st, 2022 you will experience changes to the following APIs:

  1. GET api/v1/open_graph_objects?url=https://
    • If you are using GET api/v1/open_graph_objects?url=https:// – this API will change to only return a list of the OGO ids. Here is an example of what the response of the API will look like: { “ogos”: { “id”: 12345, …. }, { “id”: 67890, …. } }
  2. GET /messages/open_group_objects/:id.json
    • If you are using GET /messages/open_group_objects/:id.json – then after the change you can use any of the OGO ids associated with a URL and this API will return a feed of messages that the user has access to relating to that link.

Note: If you have not developed custom integration with Yammer or use 3rd party software which includes specific API calls, you can safely ignore this message.

Other Updates (available now) 

In addition, if you are using the POST /message.json API and the og_url is a SharePoint URL, to receive a response with metadata for the URL you will need to call this API using an AAD token. Instructions to obtain an AAD token can be found here. Additionally, if using a SharePoint URL do not pass a thumbnail image URL to og_image as Yammer fetches the thumbnail associated with the SharePoint URL. 

What do you need to do to prepare?

If your organization is using any of the APIs listed above, ensure that you plan for this change so it does not break any custom experiences you have leveraging these Yammer APIs. Also, contact the developers of any 3rd party software that you use to make sure that they are prepared for the coming changes to these Yammer APIs.

Additional information:

TECHNICAL BULLETIN END

QuixTec provides this and other technical bulletins ‘unaltered’ from Microsoft. As an authorized Microsoft Partner, we ensure that all our solutions we deliver to you include the latest Microsoft updates.

ABOUT US: QuixTec, LLC is a U.S. certified Veteran Owned, modern DevOps organization and Microsoft Partner that specializes in Microsoft SharePoint, Office 365 expertise & HTML5 technologies for small to enterprise-sized organizations. The founder, Richard, has 30 years of experience working with several notable companies that include World Vision, Expedia, Microsoft, Levi Strauss, NASA, Boeing Aerospace, Los Alamos National Laboratory, and the U.S. Air Force, to name a few.  QuixTec is in the Seattle area. Phone today for a free consultation and project estimate:

(425) 367-9025

LEARN MORE

SharePoint Development ServicesSharePoint DevelopmentCustom Software DevelopmentMicrosoft 365 ExpertsMicrosoft 365IT Staffing ServicesIT StaffingWordPress Development Services

You May Also Like…

Change Sender Name on Yammer Notifications

Change Sender Name on Yammer Notifications

Yammer, SharePoint Development Services From Microsoft CorporationTechnical Bulletin MC380946 · Published May 16, 2022 Message Summary We are excited to rollout an update for Yammer's interactive emails. With this rollout, the sender name...

New Yammer as only option for non-admin users

New Yammer as only option for non-admin users

Yammer, SharePoint Development Services From Microsoft CorporationTechnical Bulletin MC379026 · Published May 12, 2022 Message Summary We are pleased to announce that the next phase of the new Yammer experience rollout is a month away....

Microsoft Stream: View and edit video/audio file information

Microsoft Stream: View and edit video/audio file information

OneDrive for Business, SharePoint Online, Yammer, Stream, SharePoint Development Services From Microsoft CorporationTechnical Bulletin MC353485 · Published Apr 5, 2022 Message Summary We will be updating the web player for audio &...