Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Update an existing lead in the Noojee Campaigner. Lead data is to be POSTed and encoded as json.

Entry point:

http://<server host>/servicemanager/rest/CampaignAPI/updateLead


Parameters:

ParameterDescription
fTemplateIdCampaign Template id of the Template that the lead will be associated with.
fCampaignIdCampaign id of the Campaign that the lead will be associated with.
fAllocationIdAllocation id of the Campaign that the lead will be associated with.
timeStampthe authentication timestamp.
hashthe authentication signature or hash.


System fields that can be part of the json data:

ParameterDescription
njExternalLeadIdUsed to identify the lead to be update.
njDispositionDisposition code. Any Dispositon Actions associated with the new Disposition (via the value in njDispositon) WILL be triggered .
njCallBackDate

The date on which the lead is to be called. If not specified the lead is treated as a 'new' lead and will be called on a first come first served basis.

Format is "yyyy/MM/dd HH:mm"

njPriorityA priority between 0 and 100. The lower the number the higher the priority. Higher priority leads will be called before lower priority calls. Default priority is 10.


Sample query:

curl -v -H "Accept: application/json" -H "Content-Type: application/json" -X POST -d '{"Name":"Jane Smith","StreetAddress":"Suite 8/10 Hoddle St", "City": "Abbotsford", "State":"Vic", "PostCode":"3064", "FirstPhone":"0383218199", "njExternalLeadId":"9856", "njDisposition":"Sale"}' 'http://127.0.0.1:8080/servicemanager/rest/CampaignAPI/updateLead?fTemplateId=41&fCampaignId=41&fAllocationId=38&apiKey=f863246a-973e-11e6-8784-08002718f5b5'


Sample success response:

{"code":0,"message":"Imported 0 Updated 1 Rejected 0 leads.\n\nErrors (If any):\n Name,State,PostCode,FirstPhone,City,StreetAddress,Error Reason,\n"}
  • No labels