POST /subscriptions/{subscription-id}/import_contract_term
Import previous and active contract terms.For contract terms in active state, import is allowed only if the associated subscription is active, in_trial, future or non-renewing.
This API will return an error when multi-frequency billing is enabled.
Servers
- {protocol}://{site}.{environment}:{port}/api/v2
- {protocol}://{site}-test.{environment}:{port}/api/v2
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
subscription-id |
String | Yes |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
chargebee-request-origin-device |
String | No |
The device from which the customer has made the request |
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/x-www-form-urlencoded" |
chargebee-event-webhook |
String | No |
skip only webhooks Valid values:
|
chargebee-business-entity-id |
String | No |
If the site has multiple business entities, you can use this custom HTTP header to specify the business entity for which Chargebee should perform the operation. |
chargebee-event-actions |
String | No |
skip all actions to be done on the events Valid values:
|
chargebee-request-origin-user |
String | No |
The email address of your customer/user. Use this when the email address has only ASCII characters. |
chargebee-request-origin-ip |
String | No |
The IP address of the customer where the request originated |
chargebee-request-origin-user-encoded |
String | No |
The Base64-encoded email address of your customer/user. Use this if the email address has UTF-8 characters. When this header is provided, the header chargebee-request-origin-user is ignored. |
chargebee-event-email |
String | No |
skip only emails Valid values:
|
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
contract_term |
Object | No |
Parameters for contract_term |
contract_term.id |
String | No |
Id that uniquely identifies the contract term in the site. |
contract_term.contract_start |
Integer | No |
The start date of the contract term |
contract_term.total_contract_value |
Integer | No |
The sum of the totals of all the invoices raised as part of the contract term. For Default value: 0 |
contract_term.total_contract_value_before_tax |
Integer | No |
It refers to the total amount of revenue that is expected to be generated from a specific contract term, calculated as the sum of all invoices raised during the term, regardless of payment status. It is based on past performance and the specified currency in the contract. If the subscription was imported, the value for Default value: 0 |
contract_term.total_amount_raised_before_tax |
Integer | No |
The amount raised for the contract term till the time of importing the subscription excluding tax. This amount is added to the Default value: 0 |
contract_term.action_at_term_end |
String | No |
Action to be taken when the contract term completes.
Valid values:
Default value: "renew" |
contract_term.status |
String | No |
Current status of contract * active - An actively running contract term. * completed - The contract term has run its full duration. * cancelled - The contract term was ended because:
Valid values:
|
contract_term.created_at |
Integer | No |
The date when the contract term was created. |
contract_term.total_amount_raised |
Integer | No |
The amount raised for the contract term till the time of importing the subscription. This amount is added to the Default value: 0 |
contract_term.contract_end |
Integer | No |
The end date of the contract term |
contract_term.cancellation_cutoff_period |
Integer | No |
The number of days before |
contract_term.billing_cycle |
Integer | No |
The number of billing cycles of the subscription that the contract term is for. |
contract_term_billing_cycle_on_renewal |
Integer | No |
Number of billing cycles the new contract term should run for, on contract renewal. The default value is the same as |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.