POST /subscriptions/{subscription-id}/regenerate_invoice_estimate
Regenerates the invoice for the current term of the subscription. The subscription must have status
as active
or non_renewing
. This operation is not allowed when any of the following conditions hold true for the subscription:
- An invoice exists for the current term and its
status
is notvoided
. - There are unbilled charges for the current term.
- The subscription has an advance invoice.
Response
Returns an estimate
object with one of the following components depending on the value of invoice_immediately
.
- If the value is
true
: aninvoice_estimate
object that corresponds to the regenerated invoice. - If the value is
false
: a list ofunbilled_charge_estimate
objects corresponding to all the unbilled charges created for the current term of the subscription.
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 Possible 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 Possible 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-event-email |
String | No |
skip only emails Possible values:
|
Request body fields
Name | Type | Required | Description |
---|---|---|---|
prorate |
Boolean | No |
Whether the charges should be prorated according to the term specified by |
invoice_immediately |
Boolean | No |
Only applicable when Consolidated Invoicing is enabled for the customer. Set to |
date_from |
Integer | No |
The start date of the period being invoiced. The default value is current_term_start. |
date_to |
Integer | No |
The end date of the period being invoiced. The default value is current_term_end. |
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.