POST /invoices/{invoice-id}/remove_credit_note

Removes the specified adjustment credit or refundable credit allocation applied to the invoice.

Prerequisites & Constraints

Impacts

Invoice

  • The amount_due increases by the allocations[i].allocated_amount of the credit note.
  • The amount_adjusted decreases by the allocations[i].allocated_amount of the credit note if the credit_note.type is adjustment.
  • The write_off_amount decreases by the allocations[i].allocated_amount of the credit note if the credit_note.create_reason_code is Write Off.
  • If the invoice status was payment_due, not_paid, or posted, the status does not change after the credit note is removed.
  • If the invoice status was paid:
    • The status changes to posted if the due_date is in the future.
    • The status changes to not_paid if the due date is in the past.

Credit note

  • The amount_allocated decreases and the amount_available increases by the allocations[i].allocated_amount, where i is such that allocations[i].invoice_id = invoice.id.

Implementation Notes

Before you call this API, make sure that:

Servers

Path parameters

Name Type Required Description
invoice-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:

  • "all-disabled"
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:

  • "all-disabled"
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:

  • "all-disabled"

Request body fields

Name Type Required Description
credit_note Object No

Parameters for credit_note

credit_note.id String Yes

Credit-note id.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. 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.
  3. Click Test request to test run your request to the API and see the API's response.