Sets information of a specified commenting stream, for the usage of RSS.
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.
|||categoryID||string||The identifier of the comments category to which the stream of discussion belongs.|
|||streamID||string||The unique ID of the stream to which you would like to set information. Note: the string is limited to 150 characters and is case-sensitive.|
|||streamTitle||string||The title assigned to the commenting stream. This title you assign here will be assigned to each comment posted to be used for RSS & HTML outputs.|
|||streamURL||string||The stream URL assigned to the commenting stream (usually the URL of the page where the commenting stream is presented). This URL you assign will be assigned to each comment posted to be used for RSS & HTML outputs. This URL will link back from the RSS or HTML page to the original post where the comment was added.|
Note: Gigya will verify that the streamURL belongs to your site (as configured for your API key in the Dashboard section on Gigya's website).
|||streamInfoSig||string||This field is not required the first time this method is called, when the streamTitle and streamURL fields in Gigya's DB are empty. Gigya requires this call to be signed, when overriding existing values. Calculate the signature (SHA1 signature) in the same manner as described under Generating the Signature section, using the following base string “categoryID_streamID_streamTitle_streamURL”.|
If streamTags or modeationModes are set, you must include them in this signature as well.
|Either a comma separated list or an array of tags (strings) that should be associated with the stream. The tags you assign here will be assigned to the stream, to be used to filter the top streams in comments.getTopStreams.|
An object containing string values that specify the moderation mode for different comments according to their content type (see Moderation Modes for more information).
When using this field, it is not necessary to set the moderation mode for all content types. Content types that are not referred to will retain their previous moderation state. The default state for each content type is "inherit" (the stream will use the category moderation mode settings).
|||mode||string||The value accepted for the mode are:|
The mode can be changed only by a secured request.
|moderationMode||string||Deprecated. Use moderationModes instead.|
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.