This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Working with Threads in Yammer

Owned by Former user (Deleted)
Last updated: Feb 25, 2015
2 min read

The getThread operation retrieves information of a thread.

getThread
<yammer.getThread>
	<threadId>{$ctx:threadId}</threadId>
</yammer.getThread>
Properties
  • threadId: The ID of the thread.
Sample request

Following is a sample REST/JSON request that can be handled by the getThread operation.

Sample Request for getThread 
{
	"apiUrl":"https://www.yammer.com",
	"apiToken":"y8RKAv09VSVQYFrvDBozQ",
	"responseType":"json",
	"threadId":"467030174"
}
Related Yammer documentation
https://developer.yammer.com/restapi/#rest-messages

Sample configuration

Following is a sample proxy service that illustrates how to connect to Yammer with the init operation and use the getThread operation. The sample request for this proxy can be found in the getThread sample request.

Sample Proxy
<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="yammer_getThread"
       transports="https,http"
       statistics="disable"
       trace="disable"
       startOnLoad="true">
   <target>
      <inSequence onError="faultHandlerSeq">
         <property name="apiUrl" expression="json-eval($.apiUrl)"/>
         <property name="apiToken" expression="json-eval($.apiToken)"/>
         <property name="responseType" expression="json-eval($.responseType)"/>
         <property name="threadId" expression="json-eval($.threadId)"/>
         <yammer.init>
            <apiUrl>{$ctx:apiUrl}</apiUrl>
            <apiToken>{$ctx:apiToken}</apiToken>
            <responseType>{$ctx:responseType}</responseType>
         </yammer.init>
         <yammer.getThread>
            <threadId>{$ctx:threadId}</threadId>
         </yammer.getThread>
         <respond/>
      </inSequence>
      <outSequence>
         <send/>
      </outSequence>
   </target>
   <description/>
</proxy>