Docschargebeedocs

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
  • 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. Getting Started
  3. Developer Resources
  4. Articles and FAQ
  5. API & Integration
  1. Billing
  2. Getting Started
  3. Developer Resources
  4. Articles and FAQ
  5. API & Integration

Chargebee API documentation

Problem Statement

This article points you to Chargebee’s REST APIs and client libraries for integrating with Chargebee’s subscription management system.

Solution

Chargebee provides HTTP-based REST APIs. You can use standard HTTP clients (for example, curl). Chargebee also provides API client libraries for multiple languages:

  • PHP
  • Ruby
  • Python
  • Java
  • .Net
  • Node
  • GO

Sample apps and tutorials: Chargebee API Tutorials.

Authentication: Chargebee uses HTTP Basic Auth. Use your API key as the username and leave the password empty. Get the API key from Settings > Configure Chargebee > API & Webhooks > API Keys.

API keys differ for your test site and your live site.

Request: HTTP methods (GET, POST, etc.) define the operation. Query parameters apply to GET requests; POST body provides data for create/update operations.

Response: Responses are in JSON. Chargebee does not support other response formats.

Error handling: HTTP status codes indicate success or failure. Response body contains error details in JSON. 2xx indicates success; 4xx indicates client-side errors (e.g. 400 Bad Request); 5xx indicates server-side errors. Chargebee returns the first validation error encountered; validate input on your side before calling the API when possible.

Full reference: Chargebee API Overview.

Additional Information

  • API Changelog
  • API versions
  • Chargebee Checkout JS
  • Open Source Projects
  • Implementation Partners

Related Articles

Updating the backend chargebee-typescript lib to version 2.22.0

Was this article helpful?