...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
This method is ending the short term deactivation period of a specific subscription. This method can be applied only on subscription in Short Term Not Effective life cycle state. The method can be applied on a single subscription only
Resource URL
Parameters
...
Name
...
Type
...
Description
...
token
...
String
...
The token retrieved from the login method
...
subscription_identifier
(semi-optional)
...
The subscription to be modified. The allowed subscription identifier fields are the following:
Name | Type | Description |
---|---|---|
id (semi-optional) | String | The ID of subscription |
number (semi-optional) | String | The number of subscription |
Tip |
---|
For releases prior to CRM.COM R13.0.0 the subscription_identifier is mandatory |
...
accounts_receivable_identifier
(semi-optional)
...
The accounts receivable identifier that can be used to perform the subscription modification. The allowed accounts receivable identifier fields are the following:
...
Note |
---|
The ability to use the accounts_receivable_identifier instead of the subscription_identifier is applicable only when the specified Accounts Receivable owns only one Subscription |
Tip |
---|
Available from CRM.COM R13.0.0 |
...
action_type_identifier
(optional)
...
The action type that should be used. The allowed subscription action type identifier fields are the following:
Name | Type | Description |
---|---|---|
id (semi-optional) | String | The ID of the subscription action type |
name (semi-optional) | String | The name of the subscription action type |
alternative_code (semi-optional) | String | The alternative code of the subscription action type |
...
sub_action_type_identifier
(optional)
...
The sub action type that should be used. The allowed subscription sub action type identifier fields are the following:
Name | Type | Description |
---|---|---|
id (semi-optional) | String | The ID of the subscription sub action type |
name (semi-optional) | String | The name of the subscription sub action type |
alternative_code (semi-optional) | String | The alternative code of the subscription sub action type |
...
transaction_reference_number
(optional)
...
The transaction reference number of the performed subscription action. The transaction reference number is unique against already submitted subscription actions.
Â
Tip |
---|
Available from CRM.COM R13.0.0 |
...
performed_by_user_identifier
(optional)
...
 The user that actually performed the action. The allowed user identifier fields are the following:
Name | Type | Description |
---|---|---|
id (semi-optional) | String | The ID of the user |
username (semi-optional) | String | The username of the user |
...
performed_on
(optional)
...
billing_effective_date
(optional)
...
billable_period_start_date
(optional)
...
scheduled_date
(optional)
...
The date that the action is scheduled to be executed. If not specified then the action will be executed immediately
Tip |
---|
...
udf_string_1Â
(optional)
...
User Defined Field of type String
...
udf_string_2Â
(optional)
...
User Defined Field of type String
...
udf_string_3Â
(optional)
...
User Defined Field of type String
...
udf_string_4Â
(optional)
...
User Defined Field of type String
...
udf_string_5
(optional)
...
User Defined Field of type String
...
udf_string_6Â
(optional)
...
User Defined Field of type String
...
udf_string_7
(optional)
...
User Defined Field of type String
...
udf_string_8
(optional)
...
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
...
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 |
---|
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:
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
 {
"token":"DA8FB67A8BDB47F2B7FEC75F289526DD",
"subscription_identifier":{"number":"S60113"}
} |
Response:
...
theme | Confluence |
---|---|
language | javascript |
linenumbers | true |
...
Excerpt |
---|
This method is ending the short term deactivation period of a specific subscription. This method can be applied only on subscription in Short Term Not Effective life cycle state. The method can be applied on a single subscription only |
Resource URL
Parameters
Name | Type | Description | ||||||||||||||
token | String | The token retrieved from the login method | ||||||||||||||
subscription_identifier (semi-optional) | Subscription identifier | The subscription to be modified. The allowed subscription identifier fields are the following:
| ||||||||||||||
accounts_receivable_identifier (semi-optional) | Accounts Receivable Identifier | The accounts receivable identifier that can be used to perform the subscription modification. The allowed accounts receivable identifier fields are the following:
| ||||||||||||||
action_type_identifier (optional) | Subscription action type identifier | The action type that should be used. The allowed subscription action type identifier fields are the following:
| ||||||||||||||
sub_action_type_identifier (optional) | Subscription sub action type identifier | The sub action type that should be used. The allowed subscription sub action type identifier fields are the following:
| ||||||||||||||
classification_identifier (optional) | Subscription Action Classification Identifier | The subscription action's classification. The allowed subscription action classification identifier fields are the following:
| ||||||||||||||
payment_gateway_card_identifier (optional) | Payment Gateway Card Identifier | The payment gateway card that will be used to post a payment against the accounts receivable of the subscription. Applicable and required only for Subscriptions following the "Pay before bill" payment model. The applicable payment gateway card identifier fields are the following:
| ||||||||||||||
transaction_reference_number (optional) | String | The transaction reference number of the performed subscription action. The transaction reference number is unique against already submitted subscription actions.
| ||||||||||||||
performed_by_user_identifier (optional) | User identifier | The user that actually performed the action. The allowed user identifier fields are the following:
| ||||||||||||||
performed_by_unit_identifier (optional) | Unit Identifier | The unit that performed the action. The allowed unit identifier fields are the following:
| ||||||||||||||
performed_by_business_unit_identifier (optional) | Business Unit Identifier | The business unit that performed the action. The allowed business unit identifier fields are the following:
| ||||||||||||||
performed_on (optional) | Date | The date that the action was actually performed | ||||||||||||||
billing_effective_date (optional) | Date | Determines when the subscription services that are affected by the subscription action should be billed by the billing engine. | ||||||||||||||
billable_period_start_date (optional) | Date | Determines the start date of the billable period of each subscription service (it answers to the question “from which date should I start billing this service) that is affected by the subscription action. | ||||||||||||||
scheduled_date (optional) | Date | The date that the action is scheduled to be executed. If not specified then the action will be executed immediately
| ||||||||||||||
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 | ||||||||||||||
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
|
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:
|
Expand | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
HTTP Method: POST Request: Body:
Response:
|