...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Available from CRM.COM R9.0.0
Excerpt |
---|
This method is used to create a purchase customer event in a posted life cycle state, and a spend request customer event related with that purchase customer event. In case of an error none of the customer events is created |
Resource URL
Parameters
...
Name
...
Type
...
Description
...
token
...
String
...
The token retrieved from the login method
...
accounts_receivable_identifier
(semi-optional)
...
The accounts receivable that will be related with both the purchase customer event and the spend request customer event that will be created. The allowed accounts receivable identifier fields are the following:
...
rewards_participant_identifier
(semi-optional)
...
performed_by_unit_identifier
(mandatory)
...
performed_on
(mandatory)
...
Tip |
---|
Available from CRM.COM R9.0.0 Deprecate from CRM.COM R17.0.0 |
Excerpt |
---|
This method is used to create a purchase customer event in a posted life cycle state, and a spend request customer event related with that purchase customer event. In case of an error none of the customer events is created |
Resource URL
Parameters
...
Restrictions
- It is mandatory to specify one of the semi-optional parameters. Only one of those parameters is allowed to be specified.
Response Data
...
Examples
...
title | Example 1 |
---|
HTTP Method: POST
Request:
Body:
...
theme | Confluence |
---|---|
language | javascript |
linenumbers | true |
...
Name | Type | Description |
token | String | The token retrieved from the login method |
accounts_receivable_identifier (semi-optional) | Accounts receivable Identifier | The accounts receivable that will be related with both the purchase customer event and the spend request customer event that will be created |
process_immediately
(optional)
external_system
(optional)
Defines the third party system that generates the customer event
Tip |
---|
Available from CRM.COM R10.0.0 |
intended_currency_identifier
(optional)
The currency that the user was intended to use for the customer event. If specified then it is validated against the currency of the related performed by unit (i.e. the default currency) and if they don't match then an error is throw. Note that the intended currency is not saved within CRM.COM; it is just used for validation purposes. The allowed currency identifier fields are the following:
Tip |
---|
(mandatory)
(mandatory)
fields_set
(optional)
A list of fields that should be included in the results. If not specified then all the available fields will be returned
Tip |
---|
Available from CRM.COM R10.0.0 |
...
. The allowed accounts receivable identifier fields are the following:
| ||||||||||
rewards_participant_identifier (semi-optional) | Rewards Participant Identifier | The rewards participant that will be related with both the purchase customer event and the spend request customer event that will be created. The allowed rewards participant identifier fields are the following:
| ||||||||
performed_by_unit_identifier (mandatory) | Unit Identifier | The unit that initiated both the purchase customer event and the spend request customer event that will be created. The allowed unit identifier fields are the following:
| ||||||||
performed_on (mandatory) | Date | The date that both the purchase customer event and the spend request customer event that will be created were actually performed | ||||||||
process_immediately (optional) | boolean | Defines if the customer events should be processed immediately by various business processes or not
| ||||||||
external_system (optional) | String | Defines the third party system that generates the customer event
| ||||||||
authorized_by_access_token_identifier (optional) | Access Token Identifier | The access token that was used to identify and authorized the customer. This information will be overridden if the customer was identified via an access token through this Web API call. The allowed access token identifier fields are the following:
| ||||||||
intended_currency_identifier (optional) | Currency Identifier | The currency that the user was intended to use for the customer event. If specified then it is validated against the currency of the related performed by unit (i.e. the default currency) and if they don't match then an error is throw. Note that the intended currency is not saved within CRM.COM; it is just used for validation purposes. The allowed currency identifier fields are the following:
| ||||||||
(mandatory) | Purchase Customer Event Object | Information related with the purchase customer event to be created | ||||||||
(mandatory) | Spend Request Customer Event Object | Information related with the spend request that should be created. The spend request will automatically be related with the specified purchase customer event. | ||||||||
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
|
Anchor create spend purchase customer event referred parameters create spend purchase customer event referred parameters
Referred Parameter Objects
create spend purchase customer event referred parameters | |
create spend purchase customer event referred parameters |
Include Page | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
Restrictions
- It is mandatory to specify one of the semi-optional parameters. Only one of those parameters is allowed to be specified.
Response Data
Include Page | ||||
---|---|---|---|---|
|
Examples
Expand | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||
HTTP Method: POST Request: Body:
Response:
Response:
|
Expand | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
HTTP Method: POST Request: Body:
Response:
|