GET /comments

Retrieve the list of comments sorted by the recent ones on the top.

If you want to retrieve the list of comments for an entity, for example, subscription you can filter them by passing the entity type and unique identifier for that entity, for example, subscription ID.

Servers

Request headers

Name Type Required Description
chargebee-request-origin-device String No

The device from which the customer has made the request

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.

Query parameters

Name Type Required Description
limit Integer No

The number of resources to be returned.

Default value: 10

entity_id String No

Unique identifier of the entity.

entity_type String No

Type of the entity this comment generated for.

  • order - Entity that represents an order
  • customer - Entity that represents a customer
  • invoice - Invoice description
  • business_entity - Entity that represents item of type business entity
  • plan - Entity that represents a subscription plan
  • coupon - Entity that represents a discount coupon
  • subscription - Entity that represents a subscription of a customer
  • transaction - Entity that represents a transaction.
  • addon - Entity that represents an addon
  • credit_note - Credit note description
  • quote - Entity that represents a quote

Possible values:

  • "business_entity"
  • "sales_order"
  • "order"
  • "transaction"
  • "subscription"
  • "recorded_purchase"
  • "customer"
  • "omnichannel_subscription"
  • "addon"
  • "omnichannel_subscription_item_scheduled_change"
  • "plan"
  • "omnichannel_transaction"
  • "omnichannel_subscription_item"
offset String No

Determines your position in the list for pagination. To ensure that the next page is retrieved correctly, always set offset to the value of next_offset obtained in the previous iteration of the API call.

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.