GET /custom_field_configs

The device from which the customer has made the request

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.

The email address of your customer/user. Use this when the email address has only ASCII characters.

The IP address of the customer where the request originated

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.

The number of resources to be returned.

Default value: 10

Allowed entity types for custom fields. * customer -

Entity that represents a customer. * invoice -

Entity that represents an invoice. * addon_item -

Entity that represents item of type addon. * plan -

Entity that represents a subscription plan. * subscription -

Entity that represents a subscription of a customer. * coupon -

Entity that represents a discount coupon. * charge_price -

Entity that represents charge price. * item_family -

Entity that represents item family. * addon -

Entity that represents an addon. * addon_price -

Entity that represents addon price. * credit_note -

Entity that represents a credit note. * charge_item -

Entity that represents item of type charge. * plan_item -

Entity that represents item of type plan. * quote -

Entity that represents a quote. * plan_price -

Entity that represents plan price.

Valid values:

• "plan_item"
• "quote"
• "subscription"
• "addon_price"
• "customer"
• "addon"
• "charge_price"
• "item_family"
• "plan"
• "plan_price"
• "coupon"
• "addon_item"
• "charge_item"
• "invoice"
• "credit_note"

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.