Social Media Activity Node
Social Media Activity Node
This node contains information about social media activity.
Example:
<SocialMediaActivity ActionDate="2006-09-06 15:50:10" ActionTypeID="4" ActionType="Twitter Update Status" Data="Going To Notified" />
Calling The API
The API is called via a secure HTTPS request. This HTTPS request may be a GET or POST operation. Each request must supply the authentication credentials assigned to the caller by Notified. Only requests with valid credentials will be processed. These credentials identify the caller and provide access only to a specific customer area.
The format of the call is: https://api.onlinexperiences.com/scripts/Server.nxp?LASCmd=AI:4;F:APIUTILS!50566&APIUserAuthCode={YourAuthCode}&APIUserCredentials={YourCredentials}&ShowKey={ShowKey}&FromDateTime={FromDate in YYYY-MM-DD HH:MM:SS format}&ToDateTime={ToDate in YYYY-MM-DD HH:MM:SS format}&ActivityTypeFilter={filter code list, in |OPTION|OPTION| format…}&FilterUserType={0|1|-1 where 0 = attendees, 1 = exhibitors, -1 = both}
Note: The format of the APAC Data Center is: https://api.apac.onlinexperiences.com.
Specific parameter ordering is unimportant, with the only restriction being that the first parameter MUST BE LASCmd=AI:4;F:APIUTILS!50566. All other parameters may appear in any sequence order.
Attribute |
Type |
Comment |
---|---|---|
ActionDate |
Date |
Date and time the action occurred. |
ActionTypeID |
Integer |
Identifier of the action as listed below: 1 = Twitter Request Token, 2 = Twitter Access Token, 3 = Twitter Verify, 4 = Twitter Update Status, 5 = Twitter Follow, 6 = Twitter Show, 7 = Tiwtter Search, 8 = Twitter view Lists, 9 = Twitter Rate Limit Status, 11 = LinkedIn Request Token, 12 = LinkedIn Access Token, 14 = LinkedIn View Connections, 15 = LinkedIn View Profile, 30 = View Facebook widget container page |
ActionType |
String |
Text description of the action. |
Data |
String |
Additional contextual information, such as the text of a tweet. |