Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Available from CRM.COM R5.0.0
Tip
Excerpt

This method updates leads. A single lead can be updated by each call and only if it is not with status Won or Lost. Fields which are not specified are not updated at all. Fields which are specified as null will be set as null.

...

Name

Type

Description

token

String

The token retrieved from the login method

lead_identifier
(mandatory)
Lead Identifier

The identifier of the Lead to be updated. The allowed lead identifier fields are the following:

Include Page
V4:lead_identifier
V4:lead_identifier

contact_email

(optional)

StringThe email address of the contact that will be specified on the updated lead

contact_phone

(optional)

String

The phone of the contact that will be specified on the updated lead

Tip

Available from CRM.COM R11.1.0

description

(optional)

StringA description of the lead

probability_to_win

(optional)

NumberThe probability to win the retrieved lead which can vary from 0 to 100

importance

(optional)

Lead Importance

The importance related with the leads that should be returned as a result. The allowed lead importance fields are the following: IMPORTANCE1, IMPORTANCE2, IMPORTANCE3, IMPORTANCE4, IMPORTANCE5, CUSTOM1, CUSTOM2, CUSTOM3

priority

(optional)

Lead Priority

The priority related with the leads that should be returned as a result. The allowed lead priority fields are the following: 1, 2, 3, 4, 5, 6

target_amount

(optional)

NumberThe amount that is predicted to be gained when winning the retrieved lead

status_identifier

(optional)

Lead Status Identifier

The status of the lead. The allowed lead status identifier fields are the following:

Include Page
V4:lead_status_identifier
V4:lead_status_identifier

lost_reason_identifier

(mandatory on conditions)

Lead Lost Reason Identifier

The reason that the lead was lost. This information is mandatory and applicable only if the lead is updated in a status classified as lost. The allowed lead lost reason identifier fields are the following:

Include Page
V4:lead_lost_reason_identifier
V4:lead_lost_reason_identifier

Tip

Deprecated from CRM.COM R11.1.0

billing_address_identifier

(mandatory on conditions)

Address identifier

The address that will be used as the accounts receivable billing address in case that the lead is updated to a status classified as won. This information is mandatory and applicable only if the lead is updated in a status classified as won. The allowed address identifier fields are the following:

Include Page
V4:address_identifier
V4:address_identifier

Tip

Deprecated from CRM.COM R11.1.0.

category_identifier

(optional)

Lead Category Identifier

The category of the lead. The allowed lead category identifier fields are the following:

Include Page
V4:lead_category_identifier
V4:lead_category_identifier

owned_by_group_identifier
(optional)

The identifier of the owned by group information

The owned by group information of the lead. The allowed group identifier fields are the following:

Include Page
V4:group_identifier
V4:group_identifier

privacy_level_identifier
(optional)

The identifier of the privacy level

The privacy level of the lead. The allowed privacy level identifier fields are the following:

Include Page
V4:privacy_level_identifier
V4:privacy_level_identifier

udf_string_1 

(optional)

String

User Defined Field of type String

udf_string_2 

(optional)

String

User Defined Field of type String

udf_string_3 

(optional)

String

User Defined Field of type String

udf_string_4 

(optional)

String

User Defined Field of type String

udf_string_5

(optional)

String

User Defined Field of type String

udf_string_6 

(optional)

String

User Defined Field of type String

udf_string_7

(optional)

String

User Defined Field of type String

udf_string_8

(optional)

String

User Defined Field of type String

udf_float_1

(optional)

Float

User Defined Field of type Float

udf_float_2

(optional)

Float

User Defined Field of type Float

udf_float_3

(optional)

Float

User Defined Field of type Float

udf_float_4

(optional)

Float

User Defined Field of type Float

udf_date_1 

(optional)

Date

User Defined Field of type Date

udf_date_2 

(optional)

Date

User Defined Field of type Date

udf_date_3

(optional)

Date

User Defined Field of type Date

udf_date_4

(optional)

Date

User Defined Field of type Date

start_date
(optional)

DateThe date that the lead started

expected_completion_date
(optional)

DateThe date that the lead is expected to be completed. It is automatically calculated if estimate completion time is specified.
estimated_completion_time
(optional)
Time Period ObjectThe time that is estimated to complete the lead , measured in minutes, hours, days, weeks, years. It is automatically calculated if expected completion date is specified.

source

(optional)

Lead SourceInformation related with the source of the lead
assigned_to
(optional)
Assigned to objectThe assignment information for the lead

competitors_set

(optional)

Set of Lead Competitors

A lists of all possible competitors that can reach the same Lead for the same product/goal.

Include Page
V4:Web API - Updating Sets
V4:Web API - Updating Sets

users_set

(optional)

Set of Lead Users

A list of users that are set as the team involved with the lead

Include Page
V4:Web API - Updating Sets
V4:Web API - Updating Sets

services_set

(optional)

Set of lead Services Objects

A list of services for which the lead was taken for

Include Page
V4:Web API - Updating Sets
V4:Web API - Updating Sets

physical_goods_set

(optional)

Set of lead Physical Goods Objects

A list of the physical goods for which the lead was taken for

Include Page
V4:Web API - Updating Sets
V4:Web API - Updating Sets

fields_set

(optional)

List of Strings, comma separatedA list of fields that should be included in the results. If not specified then all the available fields will be returned

...