This method imports lite registration data into the Email Accounts storage. This method imports existing lite registrations into a new or additional database. No double opt-in emails are sent when using this method, and any registrations imported via this method are not considered new registrations for reporting purposes. This is an administrative API and requires a User or Application key with the necessary permissions and can not be called with a partner secret.
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.
This method requires HTTPS.
|||string||The email address associated with this lite registration.|
|||userKey||string||The user key (or application key) of the user making the request. The userKey is located within the console. Every console user has a userKey generated for them. Additionally, every user with Admin rights to a partner can create application specific user keys via the Manage Applications option under the Admin tab. Once an application is created, the User Key and Secret for that app will be available within the apps settings.|
|||secret||string||The secret associated with the userKey (or application key) making this request.|
|||profile||JSON object||The Profile information associated with this lite registration.|
|||subscriptions||JSON object||The Subscriptions information associated with this lite registration. Note that a value can be written to the lastUpdatedSubscriptionState parameter when importing lite registrations. Otherwise, this parameter is read-only.|
|||data||JSON object||Custom data associated with this lite registration.|
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.
A field that does not contain data will not appear in the response.