Tip |
---|
Available from CRM.COM R9.0.0 |
Table of Contents | ||
---|---|---|
|
GET leads/configuration/types/list
This method returns the lead types that are allowed to be used in the system as these are defined in active Lead Definitions. Multiple lead types are returned by each call.
Resource URL
Parameters
...
Name
...
Type
...
Description
...
token
...
String
...
The token retrieved from the login method
...
group_identifier
(optional)
...
The identifier of the group that will be providing the lead type. The group is filtered against the lead types' allowed organisational units. The allowed group identifier fields are the following:
...
unit_identifier
(optional)
...
The identifier of the unit that will be providing the lead type. The unit is filtered against the lead types' allowed organisational units. The allowed unit identifier fields are the following:
...
fields_set
(optional)
...
List of Strings, comma separated
...
A list of fields that should be included in the results. If not specified then all the available fields will be returned
Response Data
...
Examples
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
HTTP Method: GET Request: Response:
|
GET leads/configuration/statuses/list
This method returns the statuses that are allowed to be used by leads of specific type. Multiple statuses are returned by each call
Resource URL
Parameters
...
Name
...
Type
...
Description
...
token
...
String
...
The token retrieved from the login method
...
lead_type_identifier
(mandatory)
...
The identifier of the type of the lead that will be using the statuses. The statuses are filtered against the allowed statuses of the specified type. The allowed lead type identifier fields are the following:
...
life_cycle_state
(optional)
...
The life cycle state that the status should have. If specified then only statuses related with the specified life cycle state will be retrieved. Life cycle state options are:
PENDING, IN PROGRESS, LOST and WON
...
fields_set
(optional)
...
List of Strings, comma separated
...
A list of fields that should be included in the results. If not specified then all the available fields will be returned
Response Data
...
Examples
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
HTTP Method: GET
Request: Response:
|
GET leads/configuration/categories/list
This method returns the lead categories that are allowed to be used by leads of a specific type. Multiple lead categories are returned by each call
Resource URL
Parameters
...
Name
...
Type
...
Description
...
token
...
String
...
The token retrieved from the login method
...
lead_type_identifier
(mandatory)
...
The identifier of the type of the lead that will be using the categories. The categories are filtered against the allowed categories of the specified type. The allowed lead type identifier fields are the following:
...
fields_set
(optional)
...
List of Strings, comma separated
...
A list of fields that should be included in the results. If not specified then all the available fields will be returned
Response Data
...
Examples
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
HTTP Method: GET
Request: Response:
|
GET leads/configuration/physical_goods/list
This method returns the physical goods that are allowed to be used by leads of specific type. Multiple physical goods are returned by each call
Resource URL
Parameters
...
Name
...
Type
...
Description
...
token
...
String
...
The token retrieved from the login method
...
lead_type_identifier
(mandatory)
...
The identifier of the type of the lead that will be using the physical goods. The physical goods are filtered against the allowed physical goods of the specified type. The allowed lead request type identifier fields are the following:
...
fields_set
(optional)
...
List of Strings, comma separated
...
A list of fields that should be included in the results. If not specified then all the available fields will be returned
Response Data
...
Examples
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
HTTP Method: GET
Request: Response:
|
GET leads/configuration/services/list
This method returns the services that are allowed to be used by leads of specific type. Multiple services are returned by each call
Resource URL
Parameters
...
Name
...
Type
...
Description
...
token
...
String
...
The token retrieved from the login method
...
lead_type_identifier
(mandatory)
...
The identifier of the type of the lead that will be using the services. The services are filtered against the allowed services of the specified type. The allowed lead type identifier fields are the following:
...
fields_set
(optional)
...
List of Strings, comma separated
...
A list of fields that should be included in the results. If not specified then all the available fields will be returned
Response Data
...
Examples
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
HTTP Method: GET
Request: Response:
|
GET leads/configuration/activity_types/list
This method returns the activity types that are allowed to be used by leads of specific type. Multiple activity types are returned by each call
Resource URL
Parameters
...
Name
...
Type
...
Description
...
token
...
String
...
The token retrieved from the login method
...
lead_type_identifier
(mandatory)
...
The identifier of the type of the lead that will be using the activity types. The activity types are filtered against the allowed activity types of the specified type. The allowed lead type identifier fields are the following:
...
fields_set
(optional)
...
List of Strings, comma separated
...
A list of fields that should be included in the results. If not specified then all the available fields will be returned
Response Data
...
Examples
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
HTTP Method: GET
Request: Response:
|
GET leads/configuration/priority_levels/list
This method returns the priority levels that are allowed to be used by leads of any type. Only priority levels defined in the active Lead Definitions and set as Supported are retrieved. Multiple priority levels are returned by each call
Resource URL
Parameters
Name | Type | Description |
token | String | The token retrieved from the login method |
fields_set (optional) | List of Strings, comma separated | A list of fields that should be included in the results. If not specified then all the available fields will be returned |
Response Data
...
Examples
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
HTTP Method: GET
Request: Response:
|
GET leads/configuration/importance_levels/list
This method returns the importance levels that are allowed to be used by leads of any type. Only importance levels defined in the active Lead Definitions and set as Supported are retrieved. Multiple importance levels are returned by each call
Resource URL
Parameters
Name | Type | Description |
token | String | The token retrieved from the login method |
fields_set (optional) | List of Strings, comma separated | A list of fields that should be included in the results. If not specified then all the available fields will be returned |
Response Data
...
Examples
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
HTTP Method: GET
Request: Response:
|
GET leads/configuration/source_types/list
This method returns the source types that are allowed to be used by leads of any type. All Source Types defined in the active Lead Definitions are retrieved. Any custom Source Type which does not have a label is not retrieved. Multiple source types are returned by each call
Resource URL
Parameters
Name | Type | Description |
token | String | The token retrieved from the login method |
fields_set (optional) | List of Strings, comma separated | A list of fields that should be included in the results. If not specified then all the available fields will be returned |
Response Data
...
Examples
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
HTTP Method: GET
Request: Response:
|
GET leads/configuration/lost_reasons/list
This method returns the lost reasons that are allowed to be used by leads of any type. All Lost Reasons defined in the active Lead Definitions are retrieved. Multiple lost reasons are returned by each call
Resource URL
Parameters
Name | Type | Description |
token | String | The token retrieved from the login method |
fields_set (optional) | List of Strings, comma separated | A list of fields that should be included in the results. If not specified then all the available fields will be returned |
Response Data
...
Examples
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
HTTP Method: GET
Request: Response:
|
GET leads/configuration/competitors/list
This method returns the competitors that are allowed to be used by leads of any type. All Competitors defined in the active Lead Definitions are retrieved. Multiple competitors are returned by each call
Resource URL
Parameters
Name | Type | Description |
token | String | The token retrieved from the login method |
fields_set (optional) | List of Strings, comma separated | A list of fields that should be included in the results. If not specified then all the available fields will be returned |
Response Data
...
Examples
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
HTTP Method: GET
Request: Response:
|
...
Panel | ||||
---|---|---|---|---|
| ||||
|