Enables retrieving raw data directly from the provider. This allows accessing provider specific information, which 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 site's responsibility to know how to use the information.
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
us1.gigya.com- For the US data center.
eu1- For the European data center.
au1- For the Australian data center.
ru1- For the Russian data center.
cn1- For the Chinese data center.
If you are not sure of your site's data center, see Finding Your Data Center.
|||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". (Note: messenger has been replaced by microsoft, however, for backward compatibility, either can be used).|
|||UID||string||The user ID of the user for whom to retrieve the information.|
(Facebook only) Deprecated! 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.
The last version of the Facebook that supported this parameter is no longer available.
|||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:|
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.
Each REST API request must contain identification and authorization parameters.
Some REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as client-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your implementation when using server-to-server REST calls, it is Recommended Best Practice to always sign the request or use a secret. A non-exhaustive list of REST APIs that this may apply to are as follows:
Please refer to the Authorization Parameters section for details.
|data||any||The data returned by the provider as-is, without any manipulation by Gigya.|
Note: Every provider returns his individual data structure.
A field that does not contain data will not appear in the response.
The above is the response to the following request: