Table of contents
Description
This method updates a user's site information.
Request URL
http[s]://socialize.gigya.com/socialize.setUserInfo
Parameters
| Required | Name | Type | Description |
| Required* | UID | string | The unique ID of the user, with which this method call is associated. This is the UID you receive from Gigya after a successful login of this user. * The UID parameter is required when you call this method through one of the following interfaces: PHP SDK, Java SDK, NET SDK or if you are using the REST API directly with Gigya's proprietary authorization method. * The UID parameter is not required when you call this method through one of the following interfaces: Android SDK, iOS SDK or if you are using an external OAuth2 SDK. Note: If you are using account linking then the UID would be your site user ID. To learn more about Social Login with account linking (best practice), please refer to the Social Login Implementation guide. |
| Required | userInfo | JSON object or string | This parameter allows you to provide Gigya with a site's user profile data. This ensures consistent user experience. Gigya uses this information for example in plugins that show user info, such as the Chat and the Comments plugins. The object may include the following fields: nickname, photoURL, thumbnailURL, firstName, lastName, gender, age, email. For example: userInfo: { firstName: "David", gender: "m", age:30 } |
Authorization Parameters
Each REST API request must contain identification and authorization parameters.
Note: the authorization parameters are required only if you are using the REST API directly. If you are using one of Gigya's SDKs then these parameters are not required, since the SDK implements the authorization method internally.
There are two methods of authorization:
- If you are using Gigya's proprietary authorization method, you will need to pass the parameters specified here. Or, if you are making a call over HTTPS then you may pass the secret parameter instead of the timestamp, nonce and sig parameters. For more information, please read the Using Gigya's REST API with our proprietary authorization method guide.
- If you are conforming with the OAuth 2.0 standard, use the method socialize.getToken instead this method, with parameters grant_type set to none and x_siteUID set to the user's site identifier. For more information, please read the Using Gigya's REST API in compliance with OAuth 2.0 guide.
Response Data
| Field | Type | Description |
| 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. |
| callId | string | Unique identifier of the transaction, for debugging purposes. |
Note: A field that does not contain data, will not appear in the response.
Response Example
{
"statusCode": 200,
"errorCode": 0,
"statusReason": "OK",
"callId": "8e6dea6eb5e34f2a98860b0ddff51408"
}
.
Comments