Registers a lead as a portal user. If the lead already exists in your account, the lead will get updated as a portal user. If the lead doesn’t exist, a new lead will get created in your account.
You may pass additional lead attributes, however, it is mandatory to pass the following attributes in the JSON body –
- Any unique lead identifier in your account (EmailAddress, Phone, mx_PAN_Number, etc.). If you pass multiple unique lead identifiers in the list, the first identifier in the list will be used to search the lead.
Note: You must pass the public authentication key you receive from the Get Public Auth Key API response. It must be passed in the API header as Authorization = <Your Auth Key>
Here’s an example of an academic portal where a user can register. On clicking the ‘Get Started’ button, the Register API gets called –
This is an optional parameter. If not passed, the default value is false. If passed as true, only new leads will be registered as portal users. An exception will be returned in case of existing leads.
Pass the Attribute (Schema names of lead fields) and Value of the lead fields you want to accept.
HTTP Response Codes
This is the status code for successful API call.
The API call was made with invalid access credentials. Check your AccessKey and SecretKey.
|400 Bad Request||
The message body on the request is not as per API specification. Make sure that content type is set to “application/json” and the JSON body has correct attribute names and structure.
|404 Not Found||
The API could not be found. Please check the API signature.
|429 Too Many Requests||
API calls exceeded the limit of 25 in 5 second(s)
|500 Internal Server Error||
The API called failed. There could be many reasons for it. Check the exception message to get more details.