This method searches and retrieves data from Gigya's Data Store using an SQL-like query. A short delay is possible between the writing of account data and its availability in queries.
When possible this API should only be used via REST. The querySig param is required and should never be added to the request on the client side, to avoid manipulation.
Note: This method is also supported in our REST API. If you wish to execute this method from your server, please refer toREST API > ds.search.
The following table lists the available parameters:
|||query||string||An SQL-like query specifying the data to retrieve. For more information, please refer to the Query language specification section in the REST API.|
|||querySig||string||A HMAC_SHA1 signature proving that the search call is coming from your client application, in order to prevent fraud. Follow the instructions in Constructing a Signature using the following base-string: query + "_" + expTime.|
Because of the sensitive data involved with constructing a signature (i.e., the use of your secret key), it is recommended that the signature not be built on the client side; rather, signatures should be constructed on the server and injected into the script.
|||expTime||string||The GMT time when the signature, provided in the querySig parameter, should expire. The expected format is the Unix time format (i.e., the number of milliseconds since Jan. 1st 1970). Gigya checks the time when the search request is received. If the time succeeds expTime, the request is considered forged.|
|||callback||function||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).