SAP Customer Data Cloud Positions


Skip to end of metadata
Go to start of metadata


The PHP SDK, not part of our core offering, provides a PHP interface for the Gigya API. The library makes it simple to integrate Gigya's services in your PHP application. This document is a practical step-by-step guide for programmers who wish to integrate the Gigya service into their PHP application. Follow the steps below to get started, and use the Library Reference while implementing.

Gigya supports:

  • PHP 7.x.
  • HHVM


Library Guide and Download

Please follow these steps to integrate this library in your PHP application:

Download and Installation


  • Clone the repo
  • Run 

    composer update

In a project

  • Run 

    composer config repositories.gigyaphpsdk git
  • Run 

    composer require gigya/php-sdk

It will now be possible to autoload Gigya PHP SDK:

use Gigya\PHP

If you are upgrading from a former version, please make sure to read the SDK's Change Log.

Next Steps

  1. Obtain Gigya's APIKey and Secret key.
  2. Include GSSDK.php in your PHP application.
  3. Log the user in.
  4. Use Gigya's API - Send Requests.
  5. Optional - Incorporate security measures.


Obtaining Gigya's APIKey and Secret key

Making API calls requires an API Key and a Secret Key which are obtained from the Site Dashboard page on the Gigya website. The Secret Key must be kept secret and never transmitted to an untrusted client or over insecure networks. The API Key and the Secret Key are required parameters in each request (further ahead in this document you will find guidance for sending requests).


Including GSSDK in your PHP Application

To get started, you'll need to add Gigya PHP SDK to your application:

  1. Copy all PHP SDK files to the same location of your PHP application path.
  2. Include the GSSDK.php file in your PHP application:
include_once "/PATH_TO/GSSDK.php";

Give the relative path to the location of the GSSDK.php file.

You should now be able to compile your project successfully.


Logging in the User

The first interaction with Gigya must always be logging in. If the user is not logged in, you cannot access their social profile nor perform social activities, such as setting their status. Sending requests requires an identified Gigya user (the identification of whom is performed using the UID parameter) with an active session. A user session is created when a user logs in via the Gigya service. Log users in through your client application using our Web SDK methods: socialize.loginsocialize.notifyLogin, or using our ready made Login Add-on.



To learn more about the login process, see Social Login.


Sending a Request

After you have logged in the user, you may use the GSRequest class to access the user profile and perform various activities. This is implemented using GSRequest's send method. The following code sends a request to set the current user's status to "I feel great":

// Define the API-Key and Secret key (the keys can be obtained from your site setup page on Gigya's website).

// Step 1 - Defining the request 
$method = "socialize.setStatus";
$request = new GSRequest($apiKey,$secretKey,$method);

// Step 2 - Adding parameters
$request->setParam("UID", "PUT-UID-HERE");  // set the "UID" parameter to user's ID
$request->setParam("status", "I feel great");  // set the "status" parameter to "I feel great"

// Step 3 - Sending the request
$response = $request->send();

// Step 4 - handling the request's response.

{    // SUCCESS! response status = OK   
     echo "Success in setStatus operation.";   

{  // Error
     echo ("Got error on setStatus: " . $response->getErrorMessage());


Step 1: Defining the request

Create a GSRequest instance:

$method = "socialize.setStatus";
$request = new GSRequest($apiKey,$secretKey,$method); 

The parameters of the GSRequest constructor are:

  1. apiKey
  2. secretKey

    Note: For instructions for obtaining these keys, see above.

  3. method - the Gigya API method to call, including namespace. For example: 'socialize.getUserInfo'. Please refer to the REST API reference for the list of available methods.


Step 2: Adding parameters

After creating the GSRequest object, use the setParam method to add parameters to the request:

$request->setParam("param1", "value1");  
$request->setParam("param2", "value2"); 

When a parameter is a complex object, use the GSObject class. See example in the Appendix below.


Note: In the REST API reference you may find the list of available Gigya API methods and the list of parameters per each method.


Step 3: Sending the request

Execute GSRequest's send method:

$response = $request->send();

The method returns a GSResponse object, which is handled in the next step.


Note: By default, requests to the Gigya API are sent using the "" domain. If your site has been set up to use another of our data centers, you have to specify that the request should be sent to the specific data center. You must add the following line of code before calling the Send method:


Where <Data_Center> is:
  • - For the US data center.
  • - For the European data center.
  • - For the Australian data center.
  • - For the Russian data center.
  • - For the Chinese data center.

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

See the GSRequest documentation for more information.


Step 3: Handling the Response

Use the GSResponse object to check the status of the response, and to receive response data:

{    // SUCCESS! response status = OK   

     echo "Success in setStatus operation.";   

{  // Error
     echo ("Got error on setStatus: " . $response->getErrorMessage());


The GSResponse object includes data fields. For each request method, the response data fields are different. Please refer to the Gigya REST API reference for the list of response data fields per method.
For example - handling a socialize.getUserInfo response:
The response of 'socialize.getUserInfo' includes a 'user' object.

// Sending 'socialize.getUserInfo' request
$request = new GSRequest($apiKey,$secretKey,"socialize.getUserInfo");
$request->setParam("UID", "PUT-UID-HERE");  // set the "UID" parameter to user's ID
$response = $request->send();

// Handle 'getUserInfo' response 
if ($response->getErrorCode()==0) 

{  // SUCCESS! response status = OK  
        $nickname = $response->getString("nickname","");
        $age= $response->getInt("age",0);
        echo ("User name: " . $nickname . "; The user's age: " . $age);	
        echo ("Got error on getUserInfo: " . $response->getErrorMessage());


Optional - Incorporating Security Measures

Validating Signatures

Signature validation is only necessary and supported when validating the signature of a response that was received on the client side and then passed to the server. Server-to-server calls do not contain the UIDSignature or signatureTimestamp properties in the response.

The Gigya service supports a mechanism to verify the authenticity of the Gigya processes, to prevent fraud. When Gigya sends you information about a user, your server needs to know that it is actually coming from Gigya. For that cause, Gigya attaches a cryptographic signature to the responses that include user information. We highly recommend validating the signature. The SigUtils class is a utility class for generating and validating signatures.

For example, Gigya signs the socialize.getUserInfo method response. The following code validates the signature received with the 'socialize.getUserInfo' method response:

// Handle 'socialize.getUserInfo' response 
if ($response->getErrorCode()==0) 

{  // SUCCESS! response status = OK
	// Validate the signature
	$valid = SigUtils::validateUserSignature($response->getString("UID",""), $response->getString("signatureTimestamp",""), 
                            $secretKey, $response->getString("UIDSignature",""));
	if ($valid)
	     echo ("signature is valid");	
	     echo ("Fraud!!!");


The parameters of the validateUserSignature method are:

  1. UID - the user's unique ID
  2. signatureTimestamp - The GMT time of the response in UNIX time format (i.e. the number of seconds since Jan. 1st 1970). The method validates that the timestamp is within five minutes of the current time on your server.
  3. secretKey - The key to verification is your partner's "Secret Key". Your secret key (provided in BASE64 encoding) is located at the bottom of the Dashboard  section on Gigya's website (Read more above).
  4. UIDSignature - the cryptographic signature.

All the parameters, with the exception of the secretKey, should be taken from the 'User' object received with the 'getUserInfo' method response.
The method returns a Boolean value, signifying if the signature is valid or not.

In a similar fashion, when using the 'getFriendsInfo' method, The method response include a collection of 'Friend' objects. Each Friend object will be signed with a cryptographic signature. To verify the signature of a friend object, please use the validateFriendSignature method.


Appendix I - Publish User Action Example

The following code sample sends a request to publish a user action to the newsfeed stream on all the connected providers which support this feature.

The socialize.publishUserAction method has a complex parameter called userAction which defines the user action data to be published. To define the userAction parameter create GSObject object and fill it with data. There are two ways to fill the GSObject with data, you can either use the put method or construct the GSObject with a JSON string, as shown in the two examples below:


Option A - Using GSObject's put method

// Publish User Action

// Defining the userAction parameter
$userAction = new GSObject();

$userAction->put("title", "This is my title");
$userAction->put("userMessage", "This is my user message");
$userAction->put("description", "This is my description");
$userAction->put("linkBack", "");

$mediaItems = new GSArray();
$mediaItems->add(new GSObject("{\"src\":\"\", \"href\":\"\",\"type\":\"image\"}"));

$userAction->put("mediaItems", $mediaItems); 

// Sending 'socialize.publishUserAction' request
$request = new GSRequest("PUT-YOUR-APIKEY-HERE", "PUT-YOUR-SECRET-KEY-HERE", "socialize.publishUserAction");
$request->setParam("userAction", $userAction); // set the "userAction" parameter
$request->setParam("UID", "PUT-UID-HERE");  // set the "UID" parameter to user's ID
$response = $request->send();


Option B - Construct a GSObject from JSON string

// Defining  the userAction parameter 
$userAction = new GSObject("{\"title\":\"This is my title\", \"userMessage\":\"This is a user message\", \"description\":\"This is a description\", 
     \"linkBack\":\"\", \"mediaItems\":[ {\"src\":\"\", \"href\":\"\",\"type\":\"image\"}]}"); 

// Sending 'socialize.publishUserAction' request
$request = new GSRequest("PUT-YOUR-APIKEY-HERE", "PUT-YOUR-SECRET-KEY-HERE", "socialize.publishUserAction");
$request->setParam("userAction", $userAction); // set the "userAction" parameter
$request->setParam("UID", "PUT-UID-HERE");  // set the "UID" parameter to user's ID
$response = $request->send();


To learn more about publishing user actions, please read the Advanced Sharing guide.


Appendix II - Demo Site

The Daily Recipe is a Gigya demo site written in PHP and JavaScript. This demo outlines how to make a web site social using Gigya's platform. The demo uses Gigya's PHP SDK and Web SDK. The demo site's code is available for you to download, use and learn about the site implementation.