New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Getting Started


  • Overview
  • Chargebee Billing Data Centers
  • Object Relationship Model
  • Understanding Sites
  • Chargebee Tech Glossary
  • Articles and FAQ

Implementing Chargebee


  • Implementation Guide
  • Go-live Checklist
  • Articles and FAQ

AI in Chargebee


  • Chargebee Agents
  • Chargebee Copilot
  • Chargebee MCP Server (Model Context Protocol)

Developer Resources


  • Developer Resources Overview
  • Articles and FAQ

Product Catalog


  • Product Catalog Overview
  • Coupons
  • Articles and FAQ

Subscriptions


  • Working with Subscriptions
  • Billing
  • Orders
  • Articles and FAQ

Customers


  • Managing Customers
  • Account Hierarchy
  • Email Notifications
  • Branding
  • Configure Multiple Languages
  • Articles and FAQ

Entitlements


  • Entitlements Overview
  • Features Overview
  • Feature Management
  • Managing Product Entitlements
  • Subscription Entitlements
  • Customer Entitlements
  • Grandfathering Entitlements
  • Articles and FAQ

Usage Based Billing


  • Understanding Usages
  • Setting up Usage Based Billing
  • Usage Alerts
  • Metered Billing
  • Articles and FAQ

Chargebee CPQ


  • Chargebee CPQ
  • Chargebee CPQ for Salesforce
  • Chargebee CPQ for HubSpot

Invoices, Credit Notes, and Quotes


  • Invoices
  • Credit Notes
  • Quotes [Legacy]
  • Transactions
  • Articles and FAQ

Taxes


  • Overview
  • Configuring Taxes
  • Country-specific Taxes
  • Articles and FAQ

Hosted Capabilities


  • Overview
  • Hosted Checkout
  • Hosted Self-Serve Portal
  • Hosted Pages Features
  • Additional Hosted Pages
  • Payment Components
  • Pricing Table
  • Managing Payments with Chargebee.js
  • Mobile-Optimized Hosted Pages
  • Articles and FAQ

Site Configuration


  • Users & Roles
  • Custom Fields & Metadata
  • Approvals
  • Mandatory Fields
  • File Attachments & Comments
  • Advanced Filter Options
  • Multicurrency Pricing
  • Multi-decimal Support
  • Configuring Reason Codes
  • Events and Webhooks
  • API Keys
  • Time Zone
  • Time Machine
  • Transfer Configurations
  • Articles and FAQ

Multi Business Entity


  • Multi Business Entity Overview
  • Customer Transfer Overview
  • Articles and FAQ

Mobile Subscriptions


  • Overview
  • Omnichannel Subscriptions
  • Omnichannel One-Time Orders
  • Mobile Subscriptions (Legacy)

Reports and Analytics


  • RevenueStory
  • Home Dashboard
  • Frequently Asked Questions
  • FAQs for Classic Reports Sunset
  • Articles and FAQ

Integrations


  • Sales
  • Customer Support and Success
  • Finance
  • Tax
  • Marketing
  • Stitch
  • Collaboration
  • Contract Management
  • Ecommerce Management
  • Articles and FAQ

Data Privacy & Security


  • Two Factor Authentication
  • SAML Single Sign-On
  • System for Cross-Domain Identity Management (SCIM)
  • EU-GDPR
  • Consent Management
  • Personal Data Management
  • Compliance Certificates
  • HIPAA Guidelines
  • PCI Recommendations and Integration Types
  • Articles and FAQ

Data Operations


  • Bulk Operations
  • Migration
  • Articles and FAQ
  1. Billing
  2. Site Configuration
  3. Articles and FAQ
  4. Metadata
  1. Billing
  2. Site Configuration
  3. Articles and FAQ
  4. Metadata

What is Meta Data?

Scope

How do I use metadata?

API does not return the metadata (JSON)

Can Metadata be retrieved in API call?

Where do I configure metadata?

How to add custom field values to coupons?

Solution

Metadata can be used to store additional information about the resources that you might need for internal reference. The Metadata can be stored only in the JSON format. You can use nested JSON objects as well.


{


 "Key-1" : "Value-1",

 "Key-2" : "Value-2"

}

Metadata can be useful for storing resource-related information that you might want to retrieve while performing an action, such as, the stock value for different shirt sizes or features that are offered with a particular plan for a SaaS service.

Metadata can be passed during the Add/Update operations, for the following entities:

  • Subscriptions
  • Customers
  • Plans
  • Addons
  • Coupons

You can add the Metadata JSON from your Chargebee account by navigating to the resource page and click on the Add link for the JSON Metadata link as in the screenshot below:

Via

image
APIs:

You can also add/update the Metadata via the APIs by using the metaData input parameter for the required resources.

image

You can't filter with metadata as a criterion, or export them. However, you can retrieve metadata via API.

GET item_prices API, does not return JSON metadata configured on the top-level item level, but only metadata configured on the lower billing period dependent price level.

i.e at the item_price point level

Note:

  • Metadata is only for your reference and will not be visible to customers.

  • If you'd like to display additional fields to the customer on the hosted pages, invoices or customer portal, you can use Custom Fields.

  • Metadata will not be a 'filter criteria', or a part of the exports. For this purpose, please use Custom Fields if necessary.

Related Articles

Is metadata supported for both items and item price points? How it is affected during the migration?

Was this article helpful?