Enables retrieving raw data directly from the provider. This allows accessing provider-specific information that is not supported by Gigya.
The response is returned exactly as it is received from the provider without translation by Gigya, so it is the developer's responsibility to know how to use the information.
Note: This method is also supported in our REST API. If you wish to execute this method from your server, please refer toREST API > socialize.getRawData.
This operation is currently supported by the following providers: Facebook*, Twitter, Yahoo, LinkedIn, Google+, Xing, Odnoklassniki, Wechat, Microsoft, Instagram and Foursquare. (Note: messenger has been replaced by microsoft, however, for backward compatibility, either can be used).
*Facebook does not support FQL requests for apps created after August 2014. If you have a newer app, instead of using this method with the 'fields' parameter to send an FQL request, you should use the 'path' parameter or use the socialize.facebookGraphOperation method.
Refer to the following links for information about the available data fields and the format of the response:
- Google+ - https://developers.google.com/+/api/latest/people/get
- LinkedIn - http://developer.linkedin.com/docs/DOC-1061
- Twitter - https://dev.twitter.com/docs/api/1/get/users/search
- Yahoo - http://developer.yahoo.com/social/rest_api_guide/extended-profile-resource.html
The following table lists the available parameters:
|||provider||string||The provider to retrieve data from. The following values are currently supported for use with this parameter: "facebook", "twitter", "yahoo", "linkedin", "googleplus", "xing", "odnoklassniki", "wechat", "microsoft", "instagram", "foursquare".|
|||UID||string||The user ID of the user for whom to retrieve the information.|
|||fields||string||(Facebook only) A comma-separated list of provider-specific fields to retrieve. If you are using Facebook's Graph API this parameter may also be used for Facebook Query Language (FQL) queries. If the string starts with "SELECT" it will run as FQL.|
|||path||string||(Facebook only) For Facebook Graph API operations, this parameter specifies the path of the API from which you want to retrieve data, e.g./me/photos. This path is appended to the base API path, which is https://graph.facebook.com, to form the request.|
You may also include parameters for the request, e.g. /v2.2/12341354253?fields=from,link.
|||dataFormat||string||Choose the preferred format of the raw data. The options are:|
Note: Not all the providers support both formats.
A reference to a callback function. Gigya calls the specified function along with the results of the API method when the API method completes.
The callback function should be defined with the following signature: functionName(Response).
The "Response Object Data Members" table below provides specification of the data that is passed to the callback function.
A string of maximum 100 characters length. The CID sets categories for transactions that can be used later for filtering reports generated by Gigya in the "Context ID" combo box. The CID allows you to associate the report information with your own internal data. For example, to identify a specific widget or page on your site/application. You should not define more than 100 different context IDs.
A developer-created object that is passed back unchanged to the application as one of the fields in the response object.
Response Object Data Members
|data||string||The data returned by the provider as-is, without any manipulation by Gigya.|
Note: Every provider returns its individual data format.