This method registers a new user at your site, in accordance with the predefined site Policies and the Schema of the Accounts Storage. On-site registration requires three API calls: 1. accounts.initRegistration, 2. accounts.register and 3. accounts.finalizeRegistration. If the finalizeRegistration parameter of accounts.register is set to 'true' then there is no need to call accounts.finalizeRegistration.
A regToken (registration token), generated by accounts.initRegistration, is required when using this method.
For registration through a social network, see accounts.socialLogin.
The following table lists the available parameters:
A string that the user enters to identify his account.
* You are required to pass only one of the parameters either username or email, depending on the specification of the site's Login Identifier policy.
The user's email address.
* You are required to pass only one of the parameters either username or email, depending on the specification of the site's Login Identifier policy. If the emailVerification policy is enabled, an email is always required during registration, regardless of the defined login identifier.
|||password||string||The user's password. Gigya validates that the password meets the complexity requirements defined in the site's Password Strength policy.|
|||regToken||string||The regToken that was returned by accounts.initRegistration or the regToken returned by accounts.login if the user tried to login before the registration process is finalized. The regToken expires one hour after it is produced.|
|||profile||Profile object||The user's profile information. The object may include site's custom fields in addition to reserved field names (as defined in the Profile object). Fields that are defined as required in the Schema, are required by this method. If not passed, the method will return a "pending registration" error and a new regToken.|
|||data||JSON object||Custom data. The purpose of this object is storing any custom data associated to the user, but which is not part of the Profile object. Gigya validates that the data fields meet the requirements that are defined in the Schema.|
|||finalizeRegistration||Boolean||If set to 'true', this API call will also finalize the registration process for the user, and the user will appear as a 'New registered user' in the user reports.|
If there are missing fields, the registration will remain pending. The default value is 'false'.
|||captchaToken||string||The CAPTCHA challenge. This parameter is required if specified so in the site's CAPTCHA policy.|
|||captchaText||string||The CAPTCHA text typed by the user. This parameter is required if specified so in the site's CAPTCHA policy.|
|||secretQuestion||string||The secret question that can be used for verification. This parameter is required if specified so in the site's requireSecurityQuestion Policy.|
|||secretAnswer||string||The answer to the secret question. This parameter is required if specified so in the site's requireSecurityQuestion Policy.|
|||lang||string||The language to use in error messages and validation emails. See also Email Templates. The language specified here is stored in the locale field of the site identity. If in the emailVerification policy the emailTemplates include a template in the specified language, the verification email sent to the user will be in this language. The same goes for the passwordReset policy.|
|||targetEnv||string||This parameter defines your client side environment, which in return determines the server response data fields. The default value of this parameter is "browser", which means that by default you receive cookie-related data in the response. |
If your client runs on mobile:
If you are calling this method using a Mobile SDK since version 2.15.6, this parameter is automatically set to "mobile" (there is no need to set it manually). In any other case, you should set this parameter to be "mobile".
As a result of setting the parameter to "mobile" the server response data fields will include: sessionToken and sessionSecret (instead of cookie related data). In such case, you should send the sessionToken and sessionSecret to your mobile client. On your client side, call GSAPI.setSession (using the Mobile SDK) to save them in the app's storage.
|||include||string||A comma-separated list of fields to include in the response. The possible values are: identities-active, identities-all, loginIDs, emails, profile, data, password and |
id_token. The default is profile so if this parameter is not used, the response will return only the Profile object.
|||sessionExpiration||integer||This parameter defines the time in seconds that Gigya should keep the login session valid for the user. To end the session when the browser closes, please assign the value '0'. If this parameter is not specified, the session is valid forever.|
Note: the value of this parameter overrides the value of the identical parameter in the Global Configuration.
|||siteUID||string||You may specify the UID to use with this account. if not specified it is auto-generated.|
Note: This parameter accepts a maximum of 252 ASCII characters (Unicode is not supported).
Records the source of the registration. The default value is the URL of the current page but it can be any string value. regSource is stored in the account and can be used by verification emails to determine which page should be opened (see accounts.set Policies). Can also be set via the Global Conf object.
Gigya defines specific error codes and messages that are used with the Accounts API. These errors are returned with the APIs, indicating that some information is incorrect or missing.
This section describes the errors that are related to this API, the reasons for each error, and the expected next step.
- Account pending registration (error code 206001) - returned when you call a method that performs social login, such as this method, and the registration process has not been finalized, or the schema defines fields as required and one or more of these fields are missing from the user Profile or data. The expected next step is: if the schema defines fields that are required and one or more of these fields are missing from the user profile or data, call accounts.setAccountInfo. If the registration process has not been finalized, call accounts.finalizeRegistration.
- CAPTCHA verification failed (error code 400021) - returned when the registration policy states that requireCaptcha is "true", and the CAPTCHA verification fails when a user tries to register.
- Login identifier exists (error code 403043) - returned when email is defined as the loginIdentifier in the accountOptions policy, and the email address received from the provider exists in the system but is associated with a different user. The expected next step: call accounts.linkAccounts to merge between the account identified by the provided UID and the account identified by the provided login credentials (loginID + password).
- Validation errors - the validationErrors object is an array of validation errors; each validation error is made up of an errorCode, a message, and a fieldName. The errorCode and message specify what error occured and the fieldName specifies which field had a validation error. When an invalid field type is used, i.e. a string instead of an integer, or if a wrong format is used, i.e. an email address that is not in a correct format, an "Invalid parameter value" error is returned (error code 400006). A validation error is returned whenever there is a data validation error regarding one of the following required fields: username, password, securityQuestion, secretAnswer, email. The expected next step is: call the API method again with the missing info.