Gigya Job Openings

reports.getCommentsStats REST

Skip to end of metadata
Go to start of metadata

Description

This API retrieves Gigya's comments statistics.

Request URL


Where <Data_Center> is:
  • us1.gigya.com - For the US data center.
  • eu1.gigya.com - For the European data center.
  • au1.gigya.com - For the Australian data center.
  • ru1.gigya.com - For the Russian data center.
  • cn1.gigya-api.cn - For the Chinese data center.

If you are not sure of your site's data center, see Finding Your Data Center.

Parameters

RequiredNameTypeDescription
startDatestringThe first day of data to include in the report (in the format "YYYY-MM-DD").
endDatestringThe last day of data to include in the report (in the format "YYYY-MM-DD").
dimensionsstring

A comma separated list of dimensions to include in the report. The report data will be grouped by these dimensions. The currently supported dimensions are: 'date', 'cid', 'categoryID', and 'streamID'.

For additional information see Reports and Analytics.

measuresstring

A comma separated list of measures (data fields) to include in the report. The currently supported measures are: 'comments'.

For additional information see Reports and Analytics.

cidstringThe cid ("context ID") lets you filter the report data by site/application context.
Each Gigya transaction may be associated with a cid (a string of maximum 100 characters length). 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.
dataFormatstringDetermines the format of the data field of the response. The options are either 'csv' (default) or 'json'.  
format string Determines the format of the response. The options are:
  • json (default)
  • jsonp - if the format is jsonp then you are required to define a callback method (see parameter below).
callback string This parameter is required only when the format parameter is set to jsonp (see above). In such cases this parameter should define the name of the callback method to be called in the response, along with the jsonp response data.
context string/JSON This parameter may be used to pass data through the current method and return it, unchanged, within the response.
dontHandleScreenSet Boolean This parameter may be used in order to suppress the showing of screen-sets as a result of API calls. Default is false.
httpStatusCodes Boolean The default value of this parameter is false, which means that the HTTP status code in Gigya's response is always 200 (OK), even if an error occurs. The error code and message is given within the response data (see below). If this parameter is set to true, the HTTP status code in Gigya's response would reflect an error, if one occurred.

Authorization Parameters

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 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:

  • accounts.login
  • socialize.login
  • accounts.notifyLogin
  • socialize.notifyLogin
  • accounts.finalizeRegistration
  • accounts.linkAccounts

Please refer to the Authorization Parameters section for details. 

 

Response Data

FieldTypeDescription
 
errorCode integer The result code of the operation. Code '0' indicates success, any other number indicates failure. For a complete list of error codes, see the Error Codes table.
errorMessage string A short textual description of an error, associated with the errorCode, for logging purposes. This field will appear in the response only in case of an error.
errorDetails string This field will appear in the response only in case of an error and will contain the exception info, if available.
fullEventName string The full name of the event that triggered the response. This is an internally used parameter that is not always returned and should not be relied upon by your implementation.
callId string Unique identifier of the transaction, for debugging purposes.
time string The time of the response represented in ISO 8601 format, i.e., yyyy-mm-dd-Thh:MM:ss.SSSZ or
statusCode integer The HTTP response code of the operation. Code '200' indicates success.
This property is deprecated and only returned for backward compatibility.
statusReason string A brief explanation of the status code.
This property is deprecated and only returned for backward compatibility.

 

headersarray of stringsThe headers of the response data.
dataCSVThe reports' data in CSV format.

A field that does not contain data will not appear in the response.

 

 

Response Example

{
  "statusCode": 200,
  "errorCode": 0,
  "statusReason": "OK",
  "callId": "e407196d23684107a613f377b996a77d",
  "time": "2015-03-22T11:42:25.943Z",
  "headers": [
    "date",
    "cid",
    "categoryID",
    "streamID",
    "comments"
  ],
  "data": "date,cid,categoryID,streamID,comments\r\n
    10/30/2011,,Comments_1,Comments_1_stream_1,4\r\n
    10/30/2011,showGSPLUGIN_2.14.0.6_VMQA5_2011_10_30__11_41_13_Firefox/6.0.2,Reviews_1,Reviews_showGSPLUGIN_2011_10,1\r\n
    10/30/2011,showGSPLUGIN_2.14.0.6_VMQA5_2011_10_30__11_38_42_Firefox/6.0.2,Comments_1,Comments_showGSPLUGIN_2011_10,2\r\n
    10/31/2011,showGSPLUGIN_2.14._VMQA4_2011_10_31__10_08_26_Chrome/14.0.835.202,Comments_1,Comments_showGSPLUGIN_2011_10,1\r\n"
}