Versions Compared

Old Version 4

changes.mady.by.user Brett Sutton (Deactivated)

Saved on

compared with

New Version 5

changes.mady.by.user Brett Sutton (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
linenumberstrue
{"code":0,"message":"OK"}

Error Codes

The API returns a HTTP status code and an json error code as follows:

HTTP status of 200 is returned when the lead was successfully inserted or updated.

HTTP status of 400 is returned when you passed some invalid data.

HTTP status of 500 is returned if our system throws an exception (our code is broken).

CodeMessageHTTP statusDescription
0OK200The lead was successfully inserted or updated.
101COULDNT_FIND_THE_LEAD400For an update, the njExternalLeadId didn't match a lead
102NO_PHONE_FIELDS400For an import the lead doesn't have and phone numbers.
103EXCEPTION400
104DNC400The lead's phone numbers are on the DNC list
105DUPLICATE400There is already a lead with this phone number
106INVALID_DISPOSTION400When updating, the supplied disposition doesn't exist.
107DISPOSTION_ISNT_SET_AND_NOCHANGE_SPECIFIED400When 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.
108IMPORT_BUT_NOCHANGE_SPECIFIED400Tried to insert a lead but a field contained the value '<NO CHANGE>' which is only valid for updates.
109TIMEOUT_TOO_MANY_CONCURRENT_REQUESTS400

There are too many concurrent insert/update API requests. Wait a bit and then retry the insert/update.

110LEAD_NOT_UPDATED_DUE_TO_CONFLICT400The 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.