When offering subscriptions of products or services, each entity that is made available for sale is represented by an “item” object. Items therefore represent the various plans, addons or charges that you offer as part of your product catalog. Non-metered items are charged upfront in Chargebee, while metered items are charged at the end of the billing cycle, based on usage.
Types of Items
There are three types of items and they’re listed and explained here. Examples for each type are provided in the table that follows.
Plan-items or Plans
Plan-items are items that have a recurring charge and are an essential component of any subscription. Typically, plans represent a principal or key product or service in your catalog. They are charged at recurring intervals and often have other products or services offered along with them as addons and charges.
Addon-items or Addons
Addon-items are items that are sold along with a plan and are charged for at recurring intervals.
Charge-items or Charges
Charge-items are items that are sold along with a plan but charged once (or each time) a specified event occurs. A charge can also be applied to a customer without attaching to a subscription.
Examples
To help understand each type of item better, listed below are some examples of items from different business domains:
Non-Metered (SaaS)
Item Family: A project management solution.
Plans:
A “basic” plan offering a small set of features.
A “business” plan offering a larger set of features.
Addons:
An analytics plugin that is available only with the “business” plan.
A reporting plugin, available with both the above plans.
Charges:
Implementation charges.
Trial charges.
Non-Metered (E-commerce)
Item Family: A printed news magazine.
Plans:
Periodic issues of the magazine.
Periodic issues of the magazine, with digital content.
Addons:
Supplementary online content.
Access to a year’s worth of back issues.
Searchable access to all back issues.
Charges:
Special edition books that are published every so often.
Metered
Item Family: SMS delivery services.
Plans:
A basic plan of up to 100K messages @ $0.03 per message.
A volume plan of 2M messages @ $0.01 per message.
Addons:
An addon of 50K MMS messages @ $0.1 per message.
Instant messaging.
Charges:
Automated Metered Billing is not applicable for charges.
optional, string, max chars=2000 Description of the item. This is visible only in Chargebee and not to customers.
Note:
The description field supports up to 2000 characters, including HTML tags. The inner text (excluding HTML tags) must not exceed 500 characters. For example: <ul><li>testing</li><li>desc</li></ul>. Total with tags: 38 characters, inner text: 'testing desc' (12 characters).
If your input includes characters requiring sanitization, such as incomplete HTML tags, the sanitization process may alter the input and increase its length. If the sanitized content exceeds the allowed limit, the request will be rejected.
optional, enumerated string The status of the item.
Possible values are
activeThe item can be used to create new item prices.archivedThe item is no longer active and no new item prices can be createddeletedIndicates that the item has been deleted. The id and name can be reused. Deleted items can be retrieved using List items.
activeThe item can be used to create new item prices.archivedThe item is no longer active and no new item prices can be createddeletedIndicates that the item has been deleted. The id and name can be reused. Deleted items can be retrieved using List items.
optional, long The version number of this resource. For every change made to the resource, resource_version is updated with a new timestamp in milliseconds.
planAn essential component of a subscription. Every subscription has exactly one plan. It has a recurring charge and its period defines the billing period of the subscription.addonA recurring component that can be added to a subscription in addition to its plan.chargeA non-recurring component that can be added to a subscription in addition to its plan. An charge can also be applied to a customer directly without being applied to a subscription.
planAn essential component of a subscription. Every subscription has exactly one plan. It has a recurring charge and its period defines the billing period of the subscription.addonA recurring component that can be added to a subscription in addition to its plan.chargeA non-recurring component that can be added to a subscription in addition to its plan. An charge can also be applied to a customer directly without being applied to a subscription.
optional, boolean, default=false Indicates that the item is a physical product. If Orders are enabled in Chargebee, subscriptions created for this item will have orders associated with them.
optional, string, max chars=500 If enabled_for_checkout, then the URL to be redirected to once the checkout is complete. This attribute is only available for plan-items.
boolean, default=true Allow the plan to subscribed to via Checkout. Applies only for plan-items. Note: Only the in-app version of Checkout is supported for Product Catalog v2.
boolean, default=true Allow customers to change their subscription to this plan via the Self-Serve Portal. Applies only for plan-items. This requires the Portal configuration to allow changing subscriptions.
optional, boolean The item is included in MRR calculations for your site. This attribute is only applicable for items of type = charge and when the feature is enabled in Chargebee. Note: If the site-level setting is to exclude charge-items from MRR calculations, this value is always returned false.
optional, enumerated string, default=all Indicates which addon-items and charge-items can be applied to the item. Only meant for plan-items. Other details of attaching items such as whether to attach as a mandatory item or to attach on a certain event, can be specified using the Create or Update an attached item API.
Possible values are
allall addon-items and charge-items are applicable to this plan-item.restrictedonly the addon-items or charge-items provided in applicable_items can be applied to this plan-item.
allall addon-items and charge-items are applicable to this plan-item.restrictedonly the addon-items or charge-items provided in applicable_items can be applied to this plan-item.
optional, string, max chars=30 The unit of measure for a quantity-based item. This is displayed on the Chargebee UI and on customer facing documents/pages. The latter includes hosted pages, invoices and quotes. Examples follow:
boolean, default=false Specifies whether the item undergoes metered billing. When true, the quantity is calculated from usage records. When false, the quantity is as determined while adding an item price to the subscription. Applicable only for items of typeplan or addon and when Metered Billing is enabled. The value of this attribute cannot be changed.
optional, enumerated string How the quantity is calculated from usage data for the item prices belonging to this item. Only applicable when the item is metered. This value overrides the one set at the site level.
Possible values are
sum_of_usagesthe net quantity is the sum of the quantity of all usages for the current term.last_usagefrom among the usage records for the item price with usage_date within the relevant billing period, the quantity of the usage record with the most recent usage_date is taken as the net quantity consumed.max_usagefrom among the usage records for the item price with usage_date within the relevant billing period, the quantity of the usage record with the maximum value is taken as the net quantity consumed.
sum_of_usagesthe net quantity is the sum of the quantity of all usages for the current term.last_usagefrom among the usage records for the item price with usage_date within the relevant billing period, the quantity of the usage record with the most recent usage_date is taken as the net quantity consumed.max_usagefrom among the usage records for the item price with usage_date within the relevant billing period, the quantity of the usage record with the maximum value is taken as the net quantity consumed.
optional, enumerated string The subscription channel this object originated from and is maintained in.
Possible values are
webThe object was created (and is maintained) for the web channel directly in Chargebee via API or UI.app_storeThe object data is synchronized with data from in-app subscription(s) created in Apple App Store. Direct manipulation of this object via UI or API is disallowed.play_storeThe object data is synchronized with data from in-app subscription(s) created in Google Play Store. Direct manipulation of this object via UI or API is disallowed.
In-App Subscriptions is currently in early access. Contact eap@chargebee.com for more information.
webThe object was created (and is maintained) for the web channel directly in Chargebee via API or UI.app_storeThe object data is synchronized with data from in-app subscription(s) created in Apple App Store. Direct manipulation of this object via UI or API is disallowed.play_storeThe object data is synchronized with data from in-app subscription(s) created in Google Play Store. Direct manipulation of this object via UI or API is disallowed.
In-App Subscriptions is currently in early access. Contact eap@chargebee.com for more information.
optional, string, max chars=50 The unique ID of the business entity of this item. This is applicable only when multiple business entities have been created for the site. The value of this attribute indicates that the resource is specific to the given business entity.
optional, list of applicable_item The list of addons and charges that are allowed to be applied to the plan. This attribute is applicable only for plan-items and that too when item_applicability is restricted.
optional, list of bundle_item The list of items(plans, addons, and charges) added to the bundle plan. This attribute is only available when the item_type is plan.
Bundle item attributes
item_id
string, max chars=100 The ID of the item(plan, addon, or charge) associated with this bundle. Note: At least one plan item must be associated with this bundle.
planAn essential component of the bundle plan. Note: At least one plan item should be associated with the bundle.addonA recurring component that can be added to a bundle plan.chargeA non-recurring component that can be added to a bundle plan.
planAn essential component of the bundle plan. Note: At least one plan item should be associated with the bundle.addonA recurring component that can be added to a bundle plan.chargeA non-recurring component that can be added to a bundle plan.
optional, bundle_configuration This attribute holds additional information about the bundle item. This attribute is only available when the item_type is plan.
Bundle configuration attributes
type
enumerated string Type of the bundle
Possible values are
fixedFixed bundle_configuration.type appears when you create a bundle plan that cannot be updated during checkout or subscription creation.
fixedFixed bundle_configuration.type appears when you create a bundle plan that cannot be updated during checkout or subscription creation.
optional, string, max chars=2000 Description of the item. This is visible only in Chargebee and not to customers.
Note:
The description field supports up to 2000 characters, including HTML tags. The inner text (excluding HTML tags) must not exceed 500 characters. For example: <ul><li>testing</li><li>desc</li></ul>. Total with tags: 38 characters, inner text: 'testing desc' (12 characters).
If your input includes characters requiring sanitization, such as incomplete HTML tags, the sanitization process may alter the input and increase its length. If the sanitized content exceeds the allowed limit, the request will be rejected.
optional, enumerated string The status of the item.
Possible values are
activeThe item can be used to create new item prices.archivedThe item is no longer active and no new item prices can be createddeletedIndicates that the item has been deleted. The id and name can be reused. Deleted items can be retrieved using List items.
activeThe item can be used to create new item prices.archivedThe item is no longer active and no new item prices can be createddeletedIndicates that the item has been deleted. The id and name can be reused. Deleted items can be retrieved using List items.
optional, long The version number of this resource. For every change made to the resource, resource_version is updated with a new timestamp in milliseconds.
planAn essential component of a subscription. Every subscription has exactly one plan. It has a recurring charge and its period defines the billing period of the subscription.addonA recurring component that can be added to a subscription in addition to its plan.chargeA non-recurring component that can be added to a subscription in addition to its plan. An charge can also be applied to a customer directly without being applied to a subscription.
planAn essential component of a subscription. Every subscription has exactly one plan. It has a recurring charge and its period defines the billing period of the subscription.addonA recurring component that can be added to a subscription in addition to its plan.chargeA non-recurring component that can be added to a subscription in addition to its plan. An charge can also be applied to a customer directly without being applied to a subscription.
optional, boolean, default=false Indicates that the item is a physical product. If Orders are enabled in Chargebee, subscriptions created for this item will have orders associated with them.
optional, string, max chars=500 If enabled_for_checkout, then the URL to be redirected to once the checkout is complete. This attribute is only available for plan-items.
boolean, default=true Allow the plan to subscribed to via Checkout. Applies only for plan-items. Note: Only the in-app version of Checkout is supported for Product Catalog v2.
boolean, default=true Allow customers to change their subscription to this plan via the Self-Serve Portal. Applies only for plan-items. This requires the Portal configuration to allow changing subscriptions.
optional, boolean The item is included in MRR calculations for your site. This attribute is only applicable for items of type = charge and when the feature is enabled in Chargebee. Note: If the site-level setting is to exclude charge-items from MRR calculations, this value is always returned false.
optional, enumerated string, default=all Indicates which addon-items and charge-items can be applied to the item. Only meant for plan-items. Other details of attaching items such as whether to attach as a mandatory item or to attach on a certain event, can be specified using the Create or Update an attached item API.
Possible values are
allall addon-items and charge-items are applicable to this plan-item.restrictedonly the addon-items or charge-items provided in applicable_items can be applied to this plan-item.
allall addon-items and charge-items are applicable to this plan-item.restrictedonly the addon-items or charge-items provided in applicable_items can be applied to this plan-item.
optional, string, max chars=30 The unit of measure for a quantity-based item. This is displayed on the Chargebee UI and on customer facing documents/pages. The latter includes hosted pages, invoices and quotes. Examples follow:
boolean, default=false Specifies whether the item undergoes metered billing. When true, the quantity is calculated from usage records. When false, the quantity is as determined while adding an item price to the subscription. Applicable only for items of typeplan or addon and when Metered Billing is enabled. The value of this attribute cannot be changed.
optional, enumerated string How the quantity is calculated from usage data for the item prices belonging to this item. Only applicable when the item is metered. This value overrides the one set at the site level.
Possible values are
sum_of_usagesthe net quantity is the sum of the quantity of all usages for the current term.last_usagefrom among the usage records for the item price with usage_date within the relevant billing period, the quantity of the usage record with the most recent usage_date is taken as the net quantity consumed.max_usagefrom among the usage records for the item price with usage_date within the relevant billing period, the quantity of the usage record with the maximum value is taken as the net quantity consumed.
sum_of_usagesthe net quantity is the sum of the quantity of all usages for the current term.last_usagefrom among the usage records for the item price with usage_date within the relevant billing period, the quantity of the usage record with the most recent usage_date is taken as the net quantity consumed.max_usagefrom among the usage records for the item price with usage_date within the relevant billing period, the quantity of the usage record with the maximum value is taken as the net quantity consumed.
optional, enumerated string The subscription channel this object originated from and is maintained in.
Possible values are
webThe object was created (and is maintained) for the web channel directly in Chargebee via API or UI.app_storeThe object data is synchronized with data from in-app subscription(s) created in Apple App Store. Direct manipulation of this object via UI or API is disallowed.play_storeThe object data is synchronized with data from in-app subscription(s) created in Google Play Store. Direct manipulation of this object via UI or API is disallowed.
In-App Subscriptions is currently in early access. Contact eap@chargebee.com for more information.
webThe object was created (and is maintained) for the web channel directly in Chargebee via API or UI.app_storeThe object data is synchronized with data from in-app subscription(s) created in Apple App Store. Direct manipulation of this object via UI or API is disallowed.play_storeThe object data is synchronized with data from in-app subscription(s) created in Google Play Store. Direct manipulation of this object via UI or API is disallowed.
In-App Subscriptions is currently in early access. Contact eap@chargebee.com for more information.
optional, string, max chars=50 The unique ID of the business entity of this item. This is applicable only when multiple business entities have been created for the site. The value of this attribute indicates that the resource is specific to the given business entity.
optional, list of applicable_item The list of addons and charges that are allowed to be applied to the plan. This attribute is applicable only for plan-items and that too when item_applicability is restricted.
optional, list of bundle_item The list of items(plans, addons, and charges) added to the bundle plan. This attribute is only available when the item_type is plan.
optional, bundle_configuration This attribute holds additional information about the bundle item. This attribute is only available when the item_type is plan.
planAn essential component of a subscription. Every subscription has exactly one plan. It has a recurring charge and its period defines the billing period of the subscription.addonA recurring component that can be added to a subscription in addition to its plan.chargeA non-recurring component that can be added to a subscription in addition to its plan. An charge can also be applied to a customer directly without being applied to a subscription.
planAn essential component of a subscription. Every subscription has exactly one plan. It has a recurring charge and its period defines the billing period of the subscription.addonA recurring component that can be added to a subscription in addition to its plan.chargeA non-recurring component that can be added to a subscription in addition to its plan. An charge can also be applied to a customer directly without being applied to a subscription.
optional, string, max chars=2000 Description of the item. This is visible only in Chargebee and not to customers.
Note:
The description field supports up to 2000 characters, including HTML tags. The inner text (excluding HTML tags) must not exceed 500 characters. For example: <ul><li>testing</li><li>desc</li></ul>. Total with tags: 38 characters, inner text: 'testing desc' (12 characters).
If your input includes characters requiring sanitization, such as incomplete HTML tags, the sanitization process may alter the input and increase its length. If the sanitized content exceeds the allowed limit, the request will be rejected.
optional, boolean, default=false Indicates that the item is a physical product. If Orders are enabled in Chargebee, subscriptions created for this item will have orders associated with them.
optional, boolean, default=true Allow customers to change their subscription to this plan via the Self-Serve Portal. Applies only for plan-items. This requires the Portal configuration to allow changing subscriptions. Only the in-app version of the Portal is supported for Product Catalog v2.
optional, string, max chars=500 If enabled_for_checkout, then the URL to be redirected to once the checkout is complete. This attribute is only available for plan-items.
optional, boolean, default=true Allow the plan to subscribed to via Checkout. Applies only for plan-items. Note: Only the in-app version of Checkout is supported for Product Catalog v2.
optional, enumerated string, default=all Indicates which addon-items and charge-items can be applied to the item. Only possible for plan-items. Other details of attaching items such as whether to attach as a mandatory item or to attach on a certain event, can be specified using the Create or Update an attached item API.
Possible values are
allall addon-items and charge-items are applicable to this plan-item.restrictedonly the addon-items or charge-items provided in applicable_items can be applied to this plan-item.
allall addon-items and charge-items are applicable to this plan-item.restrictedonly the addon-items or charge-items provided in applicable_items can be applied to this plan-item.
optional, list of string The list of ids of addon-items and charge-items that can be applied to the plan-item. This parameter can be provided only for plan-items and that too when item_applicability is restricted. Other details of attaching items can be specified using the Create or Update an attached item API.
optional, string, max chars=30 The unit of measure for a quantity-based item. This is displayed on the Chargebee UI and on customer facing documents/pages. The latter includes hosted pages, invoices and quotes. Examples follow:
optional, boolean The item is included in MRR calculations for your site. This attribute is only applicable for items of type = charge and when the feature is enabled in Chargebee. Note: If the site-level setting is to exclude charge-items from MRR calculations, this value is always returned false.
optional, boolean, default=false Specifies whether the item undergoes metered billing. When true, the quantity is calculated from usage records. When false, the quantity is as determined while adding an item price to the subscription. Applicable only for items of typeplan or addon and when Metered Billing is enabled. The value of this attribute cannot be changed.
optional, enumerated string How the quantity is calculated from usage data for the item prices belonging to this item. Only applicable when the item is metered. This value overrides the one set at the site level. .
Possible values are
sum_of_usagesthe net quantity is the sum of the quantity of all usages for the current term.last_usagefrom among the usage records for the item price with usage_date within the relevant billing period, the quantity of the usage record with the most recent usage_date is taken as the net quantity consumed.max_usagefrom among the usage records for the item price with usage_date within the relevant billing period, the quantity of the usage record with the maximum value is taken as the net quantity consumed.
sum_of_usagesthe net quantity is the sum of the quantity of all usages for the current term.last_usagefrom among the usage records for the item price with usage_date within the relevant billing period, the quantity of the usage record with the most recent usage_date is taken as the net quantity consumed.max_usagefrom among the usage records for the item price with usage_date within the relevant billing period, the quantity of the usage record with the maximum value is taken as the net quantity consumed.
optional, string, max chars=50 The unique ID of the business entity for this item. This is applicable only when multiple business entities have been created for the site. When provided, the operation will read or write data associated with the specified business entity. If not provided, the resource will be created at the site level, and the business_entity_id will not be included in the API response.
Note
An alternative way of passing this parameter is by means of a custom HTTP header.
Parameters for bundle_items_to_add. Multiple bundle_items_to_add can be passed by specifying unique indices. pass parameters as bundle_items_to_add[<param name>][<idx:0..n>]
bundle_items_to_add[item_id][0..n]
optional, string, max chars=100 item_id that needs to be added to the bundle. Note: This parameter is only applicable when the item_type is plan.
optional, enumerated string item_type that can be added to the bundle.
Possible values are
planAn essential component of the bundle plan. Note: At least one plan item must be associated with the bundle.addonA recurring component that can be added to a bundle plan.chargeA non-recurring component that can be added to a bundle plan.
planAn essential component of the bundle plan. Note: At least one plan item must be associated with the bundle.addonA recurring component that can be added to a bundle plan.chargeA non-recurring component that can be added to a bundle plan.
optional, string, max chars=2000 Description of the item. This is visible only in Chargebee and not to customers.
Note:
The description field supports up to 2000 characters, including HTML tags. The inner text (excluding HTML tags) must not exceed 500 characters. For example: <ul><li>testing</li><li>desc</li></ul>. Total with tags: 38 characters, inner text: 'testing desc' (12 characters).
If your input includes characters requiring sanitization, such as incomplete HTML tags, the sanitization process may alter the input and increase its length. If the sanitized content exceeds the allowed limit, the request will be rejected.
optional, boolean, default=false Indicates that the item is a physical product. If Orders are enabled in Chargebee, subscriptions created for this item will have orders associated with them.
optional, boolean, default=true Allow customers to change their subscription to this plan via the Self-Serve Portal. Applies only for plan-items. This requires the Portal configuration to allow changing subscriptions.
optional, string, max chars=500 If enabled_for_checkout, then the URL to be redirected to once the checkout is complete. This parameter is only meant for plan-items.
optional, boolean, default=true Allow the plan to subscribed to via Checkout. Applies only for plan-items. Note: Only the in-app version of Checkout is supported for Product Catalog v2.
optional, enumerated string, default=all Indicates which addon-items and charge-items can be applied to the item. Only possible for plan-items. Other details of attaching items such as whether to attach as a mandatory item or to attach on a certain event, can be specified using the Create or Update an attached item API.
Possible values are
allall addon-items and charge-items are applicable to this plan-item.restrictedonly the addon-items or charge-items provided in applicable_items can be applied to this plan-item.
allall addon-items and charge-items are applicable to this plan-item.restrictedonly the addon-items or charge-items provided in applicable_items can be applied to this plan-item.
optional, list of string The list of ids of addon-items and charge-items that can be applied to the plan-item. This parameter can be provided only for plan-items and that too when item_applicability is restricted. Other details of attaching items can be specified using the Create or Update an attached item API.
optional, string, max chars=30 The unit of measure for a quantity-based item. This is displayed on the Chargebee UI and on customer facing documents/pages. The latter includes hosted pages, invoices and quotes. Examples follow:
optional, boolean The item is included in MRR calculations for your site. This attribute is only applicable for items of type = charge and when the feature is enabled in Chargebee. Note: If the site-level setting is to exclude charge-items from MRR calculations, this value is always returned false.
Parameters for bundle_items_to_add. Multiple bundle_items_to_add can be passed by specifying unique indices. pass parameters as bundle_items_to_add[<param name>][<idx:0..n>]
bundle_items_to_add[item_id][0..n]
optional, string, max chars=100 item_id that needs to be added to the bundle. Note: This parameter is only applicable when the item_type is plan.
optional, enumerated string item_type that can be added to the bundle.
Possible values are
planAn essential component of the bundle plan. Note: At least one plan item must be associated with the bundle.addonA recurring component that can be added to a bundle plan.chargeA non-recurring component that can be added to a bundle plan.
planAn essential component of the bundle plan. Note: At least one plan item must be associated with the bundle.addonA recurring component that can be added to a bundle plan.chargeA non-recurring component that can be added to a bundle plan.
Parameters for bundle_items_to_update. Multiple bundle_items_to_update can be passed by specifying unique indices. pass parameters as bundle_items_to_update[<param name>][<idx:0..n>]
bundle_items_to_update[item_id][0..n]
optional, string, max chars=100 item_id that needs to be updated from the bundle plan. This attribute is only applicable when the item_type is plan.
optional, enumerated string item_type that you want to update from the bundle.
Possible values are
planAn essential component of the bundle plan. Note: At least one plan item must be associated with the bundle.addonA recurring component that can be added to a bundle plan.chargeA non-recurring component that can be added to a bundle plan.
planAn essential component of the bundle plan. Note: At least one plan item must be associated with the bundle.addonA recurring component that can be added to a bundle plan.chargeA non-recurring component that can be added to a bundle plan.
Parameters for bundle_items_to_remove. Multiple bundle_items_to_remove can be passed by specifying unique indices. pass parameters as bundle_items_to_remove[<param name>][<idx:0..n>]
bundle_items_to_remove[item_id][0..n]
optional, string, max chars=100 item_id that needs to be removed from the bundle plan. Note: This attribute is only applicable when the item_type is plan.
optional, enumerated string item_type that you want to remove from the bundle.
Possible values are
planAn essential component of the bundle plan. Note: At least one plan item must be associated with the bundle.addonA recurring component that can be added to a bundle plan.chargeA non-recurring component that can be added to a bundle plan.
planAn essential component of the bundle plan. Note: At least one plan item must be associated with the bundle.addonA recurring component that can be added to a bundle plan.chargeA non-recurring component that can be added to a bundle plan.
Returns a list of items satisfying all the conditions specified in the filter parameters below. The list is sorted by date of creation, in descending order.
This API is not enabled for live sites by default. Please contact
support to get this enabled.
optional, string, max chars=1000 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.
optional, string filter Filter items based on item id.Possible values are : Supported operators : is, is_not, starts_with, in, not_in
Example →id[is] = "basic"
+
id
Filter items based on item id. pass parameters as id[<param name>][<operator>]
id[is][operator]
id[is][operator]
optional, string, min chars=1 filter Possible values are : Supported operators :
Example →
id[is_not][operator]
id[is_not][operator]
optional, string, min chars=1 filter Possible values are : Supported operators :
Example →
id[starts_with][operator]
id[starts_with][operator]
optional, string, min chars=1 filter Possible values are : Supported operators :
Example →
id[in][operator]
id[in][operator]
optional, string filter Possible values are : Supported operators :
Example →
id[not_in][operator]
id[not_in][operator]
optional, string filter Possible values are : Supported operators :
Example →
item_family_id[<operator>]
item_family_id[<operator>]
optional, string filter Filter items based on item_family_id.Possible values are : Supported operators : is, is_not, starts_with, in, not_in
Example →item_family_id[is] = "acme"
+
item_family_id
Filter items based on item_family_id. pass parameters as item_family_id[<param name>][<operator>]
item_family_id[is][operator]
item_family_id[is][operator]
optional, string, min chars=1 filter Possible values are : Supported operators :
Example →
item_family_id[is_not][operator]
item_family_id[is_not][operator]
optional, string, min chars=1 filter Possible values are : Supported operators :
Example →
item_family_id[starts_with][operator]
item_family_id[starts_with][operator]
optional, string, min chars=1 filter Possible values are : Supported operators :
Example →
item_family_id[in][operator]
item_family_id[in][operator]
optional, string filter Possible values are : Supported operators :
Example →
item_family_id[not_in][operator]
item_family_id[not_in][operator]
optional, string filter Possible values are : Supported operators :
Example →
type[<operator>]
type[<operator>]
optional, enumerated string filter Filter items based on item type. Possible values are : plan, addon, charge Supported operators : is, is_not, in, not_in
Example →type[is] = "plan"
+
type
Filter items based on item type. pass parameters as type[<param name>][<operator>]
type[is][operator]
type[is][operator]
optional, enumerated string filter Possible values are : plan, addon, charge Supported operators :
Example →
type[is_not][operator]
type[is_not][operator]
optional, enumerated string filter Possible values are : plan, addon, charge Supported operators :
Example →
type[in][operator]
type[in][operator]
optional, string filter Possible values are : Supported operators :
Example →
type[not_in][operator]
type[not_in][operator]
optional, string filter Possible values are : Supported operators :
Example →
name[<operator>]
name[<operator>]
optional, string filter Filter items based on item name.Possible values are : Supported operators : is, is_not, starts_with
Example →name[is] = "basic"
+
name
Filter items based on item name. pass parameters as name[<param name>][<operator>]
name[is][operator]
name[is][operator]
optional, string, min chars=1 filter Possible values are : Supported operators :
Example →
name[is_not][operator]
name[is_not][operator]
optional, string, min chars=1 filter Possible values are : Supported operators :
Example →
name[starts_with][operator]
name[starts_with][operator]
optional, string, min chars=1 filter Possible values are : Supported operators :
Example →
item_applicability[<operator>]
item_applicability[<operator>]
optional, enumerated string filter Filter items based on item_applicability. Possible values are : all, restricted Supported operators : is, is_not, in, not_in
Example →item_applicability[is] = "all"
+
item_applicability
Filter items based on item_applicability. pass parameters as item_applicability[<param name>][<operator>]
item_applicability[is][operator]
item_applicability[is][operator]
optional, enumerated string filter Possible values are : all, restricted Supported operators :
Example →
item_applicability[is_not][operator]
item_applicability[is_not][operator]
optional, enumerated string filter Possible values are : all, restricted Supported operators :
Example →
item_applicability[in][operator]
item_applicability[in][operator]
optional, string filter Possible values are : Supported operators :
Example →
item_applicability[not_in][operator]
item_applicability[not_in][operator]
optional, string filter Possible values are : Supported operators :
Example →
status[<operator>]
status[<operator>]
optional, enumerated string filter Filter items based on item status. Possible values are : active, archived, deleted Supported operators : is, is_not, in, not_in
Example →status[is] = "active"
+
status
Filter items based on item status. pass parameters as status[<param name>][<operator>]
status[is][operator]
status[is][operator]
optional, enumerated string filter Possible values are : active, archived, deleted Supported operators :
Example →
status[is_not][operator]
status[is_not][operator]
optional, enumerated string filter Possible values are : active, archived, deleted Supported operators :
Example →
status[in][operator]
status[in][operator]
optional, string filter Possible values are : Supported operators :
Example →
status[not_in][operator]
status[not_in][operator]
optional, string filter Possible values are : Supported operators :
Example →
is_giftable[<operator>]
is_giftable[<operator>]
optional, enumerated string filter Specifies if gift subscriptions can be created for this item. Possible values are : true, false Supported operators : is
Example →is_giftable[is] = "true"
+
is_giftable
Specifies if gift subscriptions can be created for this item. pass parameters as is_giftable[<param name>][<operator>]
is_giftable[is][operator]
is_giftable[is][operator]
optional, enumerated string filter Possible values are : true, false Supported operators :
Example →
updated_at[<operator>]
updated_at[<operator>]
optional, timestamp(UTC) in seconds filter Filter items based on when the items were last updated.Possible values are : Supported operators : after, before, on, between
Example →updated_at[after] = "1243545465"
+
updated_at
Filter items based on when the items were last updated. pass parameters as updated_at[<param name>][<operator>]
updated_at[after][operator]
updated_at[after][operator]
optional, timestamp(UTC) in seconds filter Possible values are : Supported operators :
Example →
updated_at[before][operator]
updated_at[before][operator]
optional, timestamp(UTC) in seconds filter Possible values are : Supported operators :
Example →
updated_at[on][operator]
updated_at[on][operator]
optional, timestamp(UTC) in seconds filter Possible values are : Supported operators :
Example →
updated_at[between][operator]
updated_at[between][operator]
optional, string filter Possible values are : Supported operators :
Example →
enabled_for_checkout[<operator>]
enabled_for_checkout[<operator>]
optional, enumerated string filter Allow the plan to subscribed to via Checkout. Applies only for plan-items. Note: Only the in-app version of Checkout is supported for Product Catalog v2. Possible values are : true, false Supported operators : is
Example →enabled_for_checkout[is] = "null"
+
enabled_for_checkout
Allow the plan to subscribed to via Checkout. Applies only for plan-items. Note: Only the in-app version of Checkout is supported for Product Catalog v2. pass parameters as enabled_for_checkout[<param name>][<operator>]
enabled_for_checkout[is][operator]
enabled_for_checkout[is][operator]
optional, enumerated string filter Possible values are : true, false Supported operators :
Example →
enabled_in_portal[<operator>]
enabled_in_portal[<operator>]
optional, enumerated string filter Allow customers to change their subscription to this plan via the Self-Serve Portal. Applies only for plan-items. This requires the Portal configuration to allow changing subscriptions. Possible values are : true, false Supported operators : is
Example →enabled_in_portal[is] = "null"
+
enabled_in_portal
Allow customers to change their subscription to this plan via the Self-Serve Portal. Applies only for plan-items. This requires the Portal configuration to allow changing subscriptions. pass parameters as enabled_in_portal[<param name>][<operator>]
enabled_in_portal[is][operator]
enabled_in_portal[is][operator]
optional, enumerated string filter Possible values are : true, false Supported operators :
Example →
metered[<operator>]
metered[<operator>]
optional, enumerated string filter Specifies whether the item undergoes metered billing. When true, the quantity is calculated from usage records. When false, the quantity is as determined while adding an item price to the subscription. Applicable only for items of typeplan or addon and when Metered Billing is enabled. The value of this attribute cannot be changed. Possible values are : true, false Supported operators : is
Example →metered[is] = "true"
+
metered
Specifies whether the item undergoes metered billing. When true, the quantity is calculated from usage records. When false, the quantity is as determined while adding an item price to the subscription. Applicable only for items of typeplan or addon and when Metered Billing is enabled. The value of this attribute cannot be changed. pass parameters as metered[<param name>][<operator>]
metered[is][operator]
metered[is][operator]
optional, enumerated string filter Possible values are : true, false Supported operators :
Example →
usage_calculation[<operator>]
usage_calculation[<operator>]
optional, enumerated string filter How the quantity is calculated from usage data for the item prices belonging to this item. Only applicable when the item is metered. This value overrides the one set at the site level. . Possible values are : sum_of_usages, last_usage, max_usage Supported operators : is, is_not, in, not_in
Example →usage_calculation[is] = "SUM_OF_USAGES"
+
usage_calculation
How the quantity is calculated from usage data for the item prices belonging to this item. Only applicable when the item is metered. This value overrides the one set at the site level. . pass parameters as usage_calculation[<param name>][<operator>]
usage_calculation[is][operator]
usage_calculation[is][operator]
optional, enumerated string filter Possible values are : sum_of_usages, last_usage, max_usage Supported operators :
Example →
usage_calculation[is_not][operator]
usage_calculation[is_not][operator]
optional, enumerated string filter Possible values are : sum_of_usages, last_usage, max_usage Supported operators :
Example →
usage_calculation[in][operator]
usage_calculation[in][operator]
optional, string filter Possible values are : Supported operators :
Example →
usage_calculation[not_in][operator]
usage_calculation[not_in][operator]
optional, string filter Possible values are : Supported operators :
Example →
channel[<operator>]
channel[<operator>]
optional, enumerated string filter The subscription channel this object originated from and is maintained in. Possible values are : web, app_store, play_store Supported operators : is, is_not, in, not_in
Example →channel[is] = "APP STORE"
+
channel
The subscription channel this object originated from and is maintained in. pass parameters as channel[<param name>][<operator>]
channel[is][operator]
channel[is][operator]
optional, enumerated string filter Possible values are : web, app_store, play_store Supported operators :
Example →
channel[is_not][operator]
channel[is_not][operator]
optional, enumerated string filter Possible values are : web, app_store, play_store Supported operators :
Example →
channel[in][operator]
channel[in][operator]
optional, string filter Possible values are : Supported operators :
Example →
channel[not_in][operator]
channel[not_in][operator]
optional, string filter Possible values are : Supported operators :
Example →
business_entity_id[<operator>]
business_entity_id[<operator>]
optional, enumerated string filter The unique ID of the
business entity of this item. Learn more about all the scenarios before using this filter.
Possible values are : true, false Supported operators : is_present, is
Example →business_entity_id[is_present] = "business_entity_id"
+
business_entity_id
The unique ID of the
business entity of this item. Learn more about all the scenarios before using this filter.
pass parameters as business_entity_id[<param name>][<operator>]
business_entity_id[is_present][operator]
business_entity_id[is_present][operator]
optional, enumerated string filter Possible values are : true, false Supported operators :
Example →
business_entity_id[is][operator]
business_entity_id[is][operator]
optional, string, min chars=1 filter Possible values are : Supported operators :
Example →
include_site_level_resources[<operator>]
include_site_level_resources[<operator>]
optional, enumerated string filter
Default value is true . To exclude site-level resources in specific cases, set this parameter to false.
Possible values are : true, false Supported operators : is
Example →include_site_level_resources[is] = "null"
+
include_site_level_resources
Default value is true . To exclude site-level resources in specific cases, set this parameter to false.
pass parameters as include_site_level_resources[<param name>][<operator>]
include_site_level_resources[is][operator]
include_site_level_resources[is][operator]
optional, enumerated string filter Possible values are : true, false Supported operators :
Example →
bundle_configuration[<operator>]
bundle_configuration[<operator>]
optional, enumerated string filter Parameters of bundle_configurationPossible values are : Supported operators : type
Example →bundle_configuration[type] = "undefined"
+
bundle_configuration
Parameters of bundle_configuration pass parameters as bundle_configuration[<param name>][<operator>]
bundle_configuration[type][operator]
bundle_configuration[type][operator]
optional, enumerated string filter Type of the bundle Possible values are : fixed Supported operators : is, is_not, in, not_in
always returned optional, string, max chars=1000 This attribute is returned only if more resources are present. To fetch the next set of resources use this value for the input parameter `offset`.
Deletes an item, marking its status as deleted. This is not allowed if there are active or archived item prices under the item. Once deleted, the id and name of the item can be reused.
This API is not enabled for live sites by default. Please contact
support to get this enabled.
Notes
Sample Request
curl https://{site}.chargebee.com/api/v2/items/delete-sample/delete \
-X POST \
-u {site_api_key}:
copy
Click to Copy
curl https://{site}.chargebee.com/api/v2/items/delete-sample/delete \-X POST \
-u {site_api_key}: