Using Yammer REST API with the New Yammer

Published Sep 01 2020 10:34 AM 9,272 Views
Microsoft

Yammer is revolutionizing its platform, incorporating a deeper integration with Microsoft 365, a redesigned UX, and improved, streamlined services. In order to offer customers these new features, Yammer has changed the format of the IDs that we use for communities, users, threads, and topics. This change corresponds to a shift on our backend from a REST API structure to a GraphQL structure. The old Yammer IDs are numeric (i.e. 123456), while the new IDs are a base64 encoded JSON (i.e. eyJfdHlwZSI6Ikdyb3VwIiwiaWQiOiIxMjM0NTYifQ).

 

It's important that as we transition to the new Yammer, we maintain compatibility with our v1 API structure. Many of our customers depend on our v1 APIs for a myriad of business workflows and their end users rely on our v1 APIs to request specific actions from an admin, including posting announcements in specific communities or posting on behalf of executives (coming soon). Microsoft Power Automate also requires old Yammer IDs.

 

Our customers have informed us that their workflows break when they try to use new Yammer IDs in our v1 APIs. We have received feedback that some of our customers have developed scripts to base64 decode the new Yammer IDs themselves, while others have resorted to third-party services to attempt to extract the old Yammer ID before calling our v1 APIs.

 

We are making this change because we strive to offer the highest quality service to our customers, and believe the burden should not fall on our customers to convert between the old and new Yammer IDs. We aim to facilitate a seamless transition to the new Yammer platform.

 

In response to customer feedback, we’re very excited to announce that we’ve updated several popular v1 API endpoints to support the use of new Yammer IDs! Now, customers can use the old or the new Yammer ID and get the exact same response. See below for an example and a list of supported endpoints.

 

For instance, if you enter either the old numeric group ID (i.e. 47513632) or the corresponding new ID (i.e. eyJfdHlwZSI6Ikdyb3VwIiwiaWQiOiI0NzUxMzYzMiJ9), you receive the same JSON payload.

 

These URLs are interchangeable:
https://www.yammer.com/api/v1/users/in_group/47513632.json
https://www.yammer.com/api/v1/users/in_group/eyJfdHlwZSI6Ikdyb3VwIiwiaWQiOiI0NzUxMzYzMiJ9.json

 

 

 

Supported Endpoints

GET /groups/[:id]
PUT /groups/[:id]
DELETE /groups/[:id]
GET /groups/for_user/[:id]
GET /groups/[:id]/members
GET /users/[:id]
PUT /users/[:id]
DELETE /users/[:id]
GET /users/liked_message/[:message_id]
GET

/users/in_group/[:group_id]

GET

/messages/in_thread/[:thread_id]

GET /messages/in_group/[:group_id]

 

These endpoints are available today for a number of preview customers. You can find the Yammer APIs here.

 

Kindly contact us if you would like to join the preview group. We welcome your feedback. Please feel free to drop us a note here or email us at api@yammer.com.

11 Comments

I am so excited for customers to preview this! Great work team!

Microsoft

Nice work team! Looking forward to seeing what developers do with this new functionality!

Occasional Contributor

"Yammer is revolutionizing its platform" but is Yammer also considering upgrading its API which is quite old and not really nice to use ? Are you actively considering integrating a Yammer API to Microsoft Graph API (all other Microsoft 365 services are in Graph API) ? You are mentionning a Graph QL backend, is there a public Graph QL API available to query ?  Thanks in advance for yours answers @JessicaFrank .

New Contributor

Any plan to include the encoded IDs in the responses?

Microsoft

@Maja Sehovac Not at the moment because the way we encode the IDs may change in future updates.

Occasional Contributor

You really should let us use the graphql API or update the v1 into something usefull (for example the Microsoft Graph), we need a good api :)

It's also very confusing when you say "Supported endpoints" when for example "/groups/[:id]" isn't in the official API-specification https://developer.yammer.com/docs/messagesmy_feedjson . Is this endpoint now supported or not? Its very frustrating that so many basic endpoints are undocumented.

 

Is there a way to find the ID of the associated Microsoft Group using the V1-api? We know that you (but not we) can do it using the graphql API and that its a quite important function to build any kind of integrated experience. 
If we know the SharePoint url or Microsoft Group Id we need to have a API to find the associated Yammer group id and also vice versa

 

We also need application permissions. If the API was stronger I think we would see more innovation and usage out there, today its hard to get anyone interested in building anything due to the struggle involved

Senior Member

Good to see that the Yammer v1 API endpoints support the use of new Yammer IDs to not break existing apps.

It would be even nicer to be able to use the Microsoft Graph API (with more functionality) for Yammer. When could this happen?

Thx, @JessicaFrank

almost all Microsoft 365 services use the Microsoft Graph API. What are the future plans here from the Yammer Team?

Microsoft

Thank you all for the feedback. We're looking into Graph API and supporting Application Permissions in Azure Active Directory, I don't have a timeline to share right now, but you'll be the first to know soon as we're ready.

 

 

Occasional Visitor

It was mentioned in the article about decoding the new ID's.  Does anyone have a PowerShell example of how to do this? 

 

Using the example ID from the article, I thought it would be as simple as:

$example = "eyJfdHlwZSI6Ikdyb3VwIiwiaWQiOiIxMjM0NTYifQ"

 [System.Text.Encoding]::Unicode.GetString([System.Convert]::FromBase64String($example)) 

Occasional Visitor

For my comment above, I realized it's UTF8, not Unicode.  So the PS code should be:

 [System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String($example)) 

 

%3CLINGO-SUB%20id%3D%22lingo-sub-1625691%22%20slang%3D%22en-US%22%3EUsing%20Yammer%20REST%20API%20with%20the%20New%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1625691%22%20slang%3D%22en-US%22%3E%3CP%3EYammer%20is%20revolutionizing%20its%20platform%2C%20incorporating%20a%20deeper%20integration%20with%20Microsoft%20365%2C%20a%20redesigned%20UX%2C%20and%20improved%2C%20streamlined%20services.%20In%20order%20to%20offer%20customers%20these%20new%20features%2C%20Yammer%20has%20changed%20the%20format%20of%20the%20IDs%20that%20we%20use%20for%20communities%2C%20users%2C%20threads%2C%20and%20topics.%20This%20change%20corresponds%20to%20a%20shift%20on%20our%20backend%20from%20a%20REST%20API%20structure%20to%20a%20GraphQL%20structure.%20The%20old%20Yammer%20IDs%20are%20numeric%20(i.e.%20123456)%2C%20while%20the%20new%20IDs%20are%20a%20base64%20encoded%20JSON%20(i.e.%20eyJfdHlwZSI6Ikdyb3VwIiwiaWQiOiIxMjM0NTYifQ).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt's%20important%20that%20as%20we%20transition%20to%20the%20new%20Yammer%2C%20we%20maintain%20compatibility%20with%20our%20v1%20API%20structure.%20Many%20of%20our%20customers%20depend%20on%20our%20v1%20APIs%20for%20a%20myriad%20of%20business%20workflows%20and%20their%20end%20users%20rely%20on%20our%20v1%20APIs%20to%20request%20specific%20actions%20from%20an%20admin%2C%20including%20posting%20announcements%20in%20specific%20communities%20or%20posting%20on%20behalf%20of%20executives%20(coming%20soon).%20Microsoft%20Power%20Automate%20also%20requires%20old%20Yammer%20IDs.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOur%20customers%20have%20informed%20us%20that%20their%20workflows%20break%20when%20they%20try%20to%20use%20new%20Yammer%20IDs%20in%20our%20v1%20APIs.%20We%20have%20received%20feedback%20that%20some%20of%20our%20customers%20have%20developed%20scripts%20to%20base64%20decode%20the%20new%20Yammer%20IDs%20themselves%2C%20while%20others%20have%20resorted%20to%20third-party%20services%20to%20attempt%20to%20extract%20the%20old%20Yammer%20ID%20before%20calling%20our%20v1%20APIs.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20are%20making%20this%20change%20because%20we%20strive%20to%20offer%20the%20highest%20quality%20service%20to%20our%20customers%2C%20and%20believe%20the%20burden%20should%20not%20fall%20on%20our%20customers%20to%20convert%20between%20the%20old%20and%20new%20Yammer%20IDs.%20We%20aim%20to%20facilitate%20a%20seamless%20transition%20to%20the%20new%20Yammer%20platform.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20response%20to%20customer%20feedback%2C%20we%E2%80%99re%20very%20excited%20to%20announce%20that%20we%E2%80%99ve%20updated%20several%20popular%20v1%20API%20endpoints%20to%20support%20the%20use%20of%20new%20Yammer%20IDs!%20Now%2C%20customers%20can%20use%20the%20old%20or%20the%20new%20Yammer%20ID%20and%20get%20the%20exact%20same%20response.%20See%20below%20for%20an%20example%20and%20a%20list%20of%20supported%20endpoints.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20instance%2C%20if%20you%20enter%20either%20the%20old%20numeric%20group%20ID%20(i.e.%2047513632)%20or%20the%20corresponding%20new%20ID%20(i.e.%20eyJfdHlwZSI6Ikdyb3VwIiwiaWQiOiI0NzUxMzYzMiJ9)%2C%20you%20receive%20the%20same%20JSON%20payload.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThese%20URLs%20are%20interchangeable%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.yammer.com%2Fapi%2Fv1%2Fusers%2Fin_group%2F47513632.json%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fwww.yammer.com%2Fapi%2Fv1%2Fusers%2Fin_group%2F47513632.json%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.yammer.com%2Fapi%2Fv1%2Fusers%2Fin_group%2FeyJfdHlwZSI6Ikdyb3VwIiwiaWQiOiI0NzUxMzYzMiJ9.json%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fwww.yammer.com%2Fapi%2Fv1%2Fusers%2Fin_group%2FeyJfdHlwZSI6Ikdyb3VwIiwiaWQiOiI0NzUxMzYzMiJ9.json%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CDIV%20style%3D%22position%3A%20relative%3B%20padding-bottom%3A%2056.25%25%3B%20padding-top%3A%2030px%3B%20height%3A%200%3B%20overflow%3A%20hidden%3B%20min-width%3A%20320px%3B%22%3E%3CIFRAME%20src%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fvideoplayer%2Fembed%2FRE4ELKc%3Fautoplay%3Dfalse%22%20frameborder%3D%220%22%20allowfullscreen%3D%22allowfullscreen%22%20style%3D%22position%3A%20absolute%3B%20top%3A%200%3B%20left%3A%200%3B%20width%3A%20100%25%3B%20height%3A%20100%25%3B%22%20class%3D%22video-iframe%22%20your%3D%22%22%20video%3D%22%22%20title%3D%22%E2%80%9Dput%22%20here%3D%22%22%3E%3C%2FIFRAME%3E%3C%2FDIV%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ESupported%20Endpoints%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CTABLE%20class%3D%22lia-align-left%22%20style%3D%22height%3A%20270px%3B%20width%3A%20400px%3B%22%20border%3D%220%22%20width%3D%22100%25%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20width%3D%2230%25%22%20height%3D%2230px%22%3EGET%3C%2FTD%3E%0A%3CTD%20width%3D%2230%25%22%20height%3D%2230px%22%3E%2Fgroups%2F%5B%3Aid%5D%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%2230%25%22%20height%3D%2230px%22%3EPUT%3C%2FTD%3E%0A%3CTD%20width%3D%2230%25%22%20height%3D%2230px%22%3E%2Fgroups%2F%5B%3Aid%5D%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%2230%25%22%20height%3D%2230px%22%3EDELETE%3C%2FTD%3E%0A%3CTD%20width%3D%2230%25%22%20height%3D%2230px%22%3E%2Fgroups%2F%5B%3Aid%5D%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%2230%25%22%20height%3D%2230px%22%3EGET%3C%2FTD%3E%0A%3CTD%20width%3D%2230%25%22%20height%3D%2230px%22%3E%2Fgroups%2Ffor_user%2F%5B%3Aid%5D%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20height%3D%2230px%22%3EGET%3C%2FTD%3E%0A%3CTD%20height%3D%2230px%22%3E%2Fgroups%2F%5B%3Aid%5D%2Fmembers%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20height%3D%2230px%22%3EGET%3C%2FTD%3E%0A%3CTD%20height%3D%2230px%22%3E%2Fusers%2F%5B%3Aid%5D%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20height%3D%2230px%22%3EPUT%3C%2FTD%3E%0A%3CTD%20height%3D%2230px%22%3E%2Fusers%2F%5B%3Aid%5D%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20height%3D%2230px%22%3EDELETE%3C%2FTD%3E%0A%3CTD%20height%3D%2230px%22%3E%2Fusers%2F%5B%3Aid%5D%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20height%3D%2230px%22%3EGET%3C%2FTD%3E%0A%3CTD%20height%3D%2230px%22%3E%2Fusers%2Fliked_message%2F%5B%3Amessage_id%5D%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20height%3D%2230px%22%3EGET%3C%2FTD%3E%0A%3CTD%20height%3D%2230px%22%3E%3CP%3E%2Fusers%2Fin_group%2F%5B%3Agroup_id%5D%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20height%3D%2230px%22%3EGET%3C%2FTD%3E%0A%3CTD%20height%3D%2230px%22%3E%3CP%3E%2Fmessages%2Fin_thread%2F%5B%3Athread_id%5D%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20height%3D%2230px%22%3EGET%3C%2FTD%3E%0A%3CTD%20height%3D%2230px%22%3E%2Fmessages%2Fin_group%2F%5B%3Agroup_id%5D%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThese%20endpoints%20are%20available%20today%20for%20a%20number%20of%20preview%20customers.%20You%20can%20find%20the%20Yammer%20APIs%20%3CA%20href%3D%22https%3A%2F%2Fdeveloper.yammer.com%2Fdocs%2Fmessagesmy_feedjson%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EKindly%20contact%20us%20if%20you%20would%20like%20to%20join%20the%20preview%20group.%20We%20welcome%20your%20feedback.%20Please%20feel%20free%20to%20drop%20us%20a%20note%20here%20or%20email%20us%20at%20%3CA%20href%3D%22mailto%3Aapi%40yammer.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Eapi%40yammer.com%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1625691%22%20slang%3D%22en-US%22%3E%3CP%3EYammer%20has%20changed%20the%20format%20of%20the%20IDs%20that%20we%20use%20for%20communities%2C%20users%2C%20threads%2C%20and%20topics.%20This%20change%20corresponds%20to%20a%20shift%20on%20our%20backend%20from%20a%20REST%20API%20structure%20to%20a%20GraphQL%20structure.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22CLO20_Terry_002.jpg%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F215867iBBAE155B311F5096%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22CLO20_Terry_002.jpg%22%20alt%3D%22CLO20_Terry_002.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1625691%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAPI%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EYammer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1625888%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Yammer%20REST%20API%20with%20the%20New%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1625888%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20so%20excited%20for%20customers%20to%20preview%20this!%20Great%20work%20team!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1625894%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Yammer%20REST%20API%20with%20the%20New%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1625894%22%20slang%3D%22en-US%22%3E%3CP%3ENice%20work%20team!%20Looking%20forward%20to%20seeing%20what%20developers%20do%20with%20this%20new%20functionality!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1628139%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Yammer%20REST%20API%20with%20the%20New%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1628139%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%22Yammer%20is%20revolutionizing%20its%20platform%22%20but%20is%20Yammer%20also%20considering%20upgrading%20its%20API%20which%20is%20quite%20old%20and%20not%20really%20nice%20to%20use%20%3F%20Are%20you%20actively%20considering%20integrating%20a%20Yammer%20API%20to%20Microsoft%20Graph%20API%20(all%20other%20Microsoft%20365%20services%20are%20in%20Graph%20API)%20%3F%20You%20are%20mentionning%20a%20Graph%20QL%20backend%2C%20is%20there%20a%20public%20Graph%20QL%20API%20available%20to%20query%20%3F%26nbsp%3B%20Thanks%20in%20advance%20for%20yours%20answers%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F777504%22%20target%3D%22_blank%22%3E%40JessicaFrank%3C%2FA%3E%26nbsp%3B.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1632517%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Yammer%20REST%20API%20with%20the%20New%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1632517%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20plan%20to%20include%20the%20encoded%20IDs%20in%20the%20responses%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1632668%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Yammer%20REST%20API%20with%20the%20New%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1632668%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F956%22%20target%3D%22_blank%22%3E%40Maja%20Sehovac%3C%2FA%3E%26nbsp%3BNot%20at%20the%20moment%20because%20the%20way%20we%20encode%20the%20IDs%20may%20change%20in%20future%20updates.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1640236%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Yammer%20REST%20API%20with%20the%20New%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1640236%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20really%20should%20let%20us%20use%20the%20graphql%20API%20or%20update%20the%20v1%20into%20something%20usefull%20(for%20example%20the%20Microsoft%20Graph)%2C%20we%20need%20a%20good%20api%20%3A)%3C%2Fimg%3E%3CBR%20%2F%3E%3CBR%20%2F%3EIt's%20also%20very%20confusing%20when%20you%20say%20%22Supported%20endpoints%22%20when%20for%20example%20%22%3CSPAN%3E%3CSTRONG%3E%2Fgroups%2F%5B%3Aid%5D%3C%2FSTRONG%3E%22%20isn't%20in%20the%20official%20API-specification%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdeveloper.yammer.com%2Fdocs%2Fmessagesmy_feedjson%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdeveloper.yammer.com%2Fdocs%2Fmessagesmy_feedjson%3C%2FA%3E%3C%2FSPAN%3E%26nbsp%3B.%20Is%20this%20endpoint%20now%20supported%20or%20not%3F%20Its%20very%20frustrating%20that%20so%20many%20basic%20endpoints%20are%20undocumented.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIs%20there%20a%20way%20to%20find%20the%20ID%20of%20the%20associated%20Microsoft%20Group%20using%20the%20V1-api%3F%20We%20know%20that%20you%20(but%20not%20we)%20can%20do%20it%20using%20the%20graphql%20API%20and%20that%20its%20a%20quite%20important%20function%20to%20build%20any%20kind%20of%20integrated%20experience.%26nbsp%3B%3CBR%20%2F%3EIf%20we%20know%20the%20SharePoint%20url%20or%20Microsoft%20Group%20Id%20we%20need%20to%20have%20a%20API%20to%20find%20the%20associated%20Yammer%20group%20id%20and%20also%20vice%20versa%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWe%20also%20need%20application%20permissions.%20If%20the%20API%20was%20stronger%20I%20think%20we%20would%20see%20more%20innovation%20and%20usage%20out%20there%2C%20today%20its%20hard%20to%20get%20anyone%20interested%20in%20building%20anything%20due%20to%20the%20struggle%20involved%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1642527%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Yammer%20REST%20API%20with%20the%20New%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1642527%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20to%20see%20that%20the%26nbsp%3B%3CSPAN%3EYammer%20v1%20API%20endpoints%20support%20the%20use%20of%20new%20Yammer%20IDs%20to%20not%20break%20existing%20apps.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIt%20would%20be%20even%20nicer%20to%20be%20able%20to%20use%20the%20Microsoft%20Graph%20API%20(with%20more%20functionality)%20for%20Yammer.%20When%20could%20this%20happen%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThx%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F777504%22%20target%3D%22_blank%22%3E%40JessicaFrank%3C%2FA%3E!%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1643216%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Yammer%20REST%20API%20with%20the%20New%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1643216%22%20slang%3D%22en-US%22%3E%3CP%3Ealmost%20all%20Microsoft%20365%20services%20use%20the%20Microsoft%20Graph%20API.%20What%20are%20the%20future%20plans%20here%20from%20the%20Yammer%20Team%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1646684%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Yammer%20REST%20API%20with%20the%20New%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1646684%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20all%20for%20the%20feedback.%20We're%20looking%20into%20Graph%20API%20and%20supporting%20Application%20Permissions%20in%20Azure%20Active%20Directory%2C%20I%20don't%20have%20a%20timeline%20to%20share%20right%20now%2C%20but%20you'll%20be%20the%20first%20to%20know%20soon%20as%20we're%20ready.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1679138%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Yammer%20REST%20API%20with%20the%20New%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1679138%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20was%20mentioned%20in%20the%20article%20about%20decoding%20the%20new%20ID's.%26nbsp%3B%20Does%20anyone%20have%20a%20PowerShell%20example%20of%20how%20to%20do%20this%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsing%20the%20example%20ID%20from%20the%20article%2C%20I%20thought%20it%20would%20be%20as%20simple%20as%3A%3C%2FP%3E%3CP%3E%24example%20%3D%20%22%3CSPAN%3EeyJfdHlwZSI6Ikdyb3VwIiwiaWQiOiIxMjM0NTYifQ%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%5BSystem.Text.Encoding%5D%3A%3AUnicode.GetString(%5BSystem.Convert%5D%3A%3AFromBase64String(%24example))%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1699937%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20Yammer%20REST%20API%20with%20the%20New%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1699937%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20my%20comment%20above%2C%20I%20realized%20it's%20UTF8%2C%20not%20Unicode.%26nbsp%3B%20So%20the%20PS%20code%20should%20be%3A%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%5BSystem.Text.Encoding%5D%3A%3A%3CSTRONG%3EUTF8%3C%2FSTRONG%3E.GetString(%5BSystem.Convert%5D%3A%3AFromBase64String(%24example))%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Sep 01 2020 10:56 AM
Updated by: