Update an existing lead in Noojee Contact.
...
As the UpdateLeadFast end point allows you to set a disposition a lead may in fact never by dialed as you can close a lead out using the appropriate disposition.
The endpoint InsertLeadFast replaces the original InsertLead method. The new endpoint takes the same arguments but has enhanced error codes and as the name implies is faster than the original InsertLead endpoint.
Performance considerations
...
| Parameter | Description | Required |
| njDisposition | Disposition code. Any Dispositon Actions associated with the new Disposition (via the value in njDispositon) WILL be triggered . | Yes |
| 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" | No |
| njPriority | A 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. | No |
| Phone Number | Whilst not a system field, you MUST specify at least on of the phone fields. However if you don't want to change the existing field value you can simply pass the value '<No Change>' as the value for any phone field. Note: the angle brackets '<>' are required. | Yes |
...
| Code | Message | HTTP status | Description |
|---|---|---|---|
| 0 | OK | 200 | The lead was successfully inserted or updated. |
| 101 | COULDNT_FIND_THE_LEAD | 400 | For an update, the njExternalLeadId didn't match a lead |
| 102 | NO_PHONE_FIELDS | 400 | For an import the lead doesn't have and phone numbers. |
| 103 | EXCEPTION | 500 | |
| 104 | DNC | 400 | The lead's phone numbers are on the DNC list |
| 105 | DUPLICATE | 400 | There is already a lead with this phone number |
| 106 | INVALID_DISPOSTION | 400 | When updating, the supplied disposition doesn't exist. |
| 107 | DISPOSTION_ISNT_SET_AND_NOCHANGE_SPECIFIED | 400 | When updating a a lead the disposition can be omitted, and <NO CHANGE> specified. But this is an error condition if the lead doesn't already have a disposition. |
| 108 | IMPORT_BUT_NOCHANGE_SPECIFIED | 400 | Tried to insert a lead but a field contained the value '<NO CHANGE>' which is only valid for updates. |
| 109 | TIMEOUT_TOO_MANY_CONCURRENT_REQUESTS | 400 | There are too many concurrent insert/update API requests. Wait a bit and then retry the insert/update. Currently a call will timeout if it is delayed by more than 1 minute. |
| 110 | LEAD_NOT_UPDATED_DUE_TO_CONFLICT | 400 | The lead update caused a conflict with another update and failed. This usually means that a user was editing the lead whilst you were trying to update it via the api. This type of issues should be rare as in most cases the user will see the error not the api. When the user sees the error they will be given the opportunity to merge the two leads via a specialised merge lead screen. If the api recieves this error then you will need to manually intervene to ensure that data isn't over-written which a simply retry is likely to do. |
...