Chargebee connector icon

Chargebee Connector

Embed Chargebee billing in your SaaS to let customers create and manage subscriptions, complete checkouts, view invoices and pay—all without leaving your app. Use Cyclr to build low-code workflows that create or update subscriptions, post invoices, capture payments and react to Chargebee events.

Build with this Connector Talk to an integration expert
01

Embed billing natively

Customers manage subscriptions inside your app.

02

Automate lifecycle events

Trigger app updates from subscription and invoice events.

03

Multi-tenant governance

Centralize keys, audits and per-tenant controls.

04

Embedded experience

Deliver customer-facing workflows natively inside your SaaS product.

CONNECTOR OVERVIEW

What you can integrate or automate with Chargebee

Teams can integrate and automate Chargebee subscription lifecycle, customer records, invoices, payments, hosted pages and product catalog operations. Use Cyclr’s low-code orchestration to create subscriptions, generate invoices, capture payments and respond to Chargebee events (for example subscription_changed or invoice_paid) so your app, CRM and downstream systems stay synchronized.

PRODUCT USE CASES

Top Use Cases for Chargebee Integrations

Quickly create integrations between your SaaS and Chargebee with Cyclr’s low-code builder. Publish your Chargebee integration in-app using Cyclr’s white label embedded marketplace to let customers self-serve subscriptions, billing pages, and invoice history inside your product.

Provision subscription during customer onboarding

Create customer and subscription records in Chargebee when a new account is created; attach plans, trial periods and payment method.

Sync invoices and payments for reconciliation

List and retrieve invoices and payments to reconcile revenue, update AR systems or generate accounting entries.

Embed hosted billing pages

Deliver Chargebee hosted pages inside your app for checkout, payment updates and plan changes, then capture resulting events.

ORCHESTRATION

How Chargebee works with Cyclr

Cyclr sits between your SaaS product and Chargebee to handle authentication, govern access and orchestrate every API call per customer, at scale.

  1. 1

    Your SaaS product

    Your app requests an action for a specific customer.

  2. 2

    Cyclr orchestration

    Cyclr authenticates, applies policies and routes the request.

  3. 3

    Chargebee

    Chargebee processes the request and returns a response to your app.

Customer-specific authentication · Governed data movement · Centralized visibility and audit

CONNECTOR COVERAGE

Available connector capabilities

Explore Chargebee methods you can orchestrate through Cyclr.

Connector actions1

List Transactions

Action

Retrieve a list of Transactions.

Customers4

List Customers

Action

Retrieve a list of Customers.

Get Customer

Action

Retrieve a Customer.

Update Customer

Action

Updates the customer resource.

List Updated Customers

Action

Retrieve a list of Customers created or updated since last run.

Invoices6

List Updated Invoices

Action

Retrieve a list of Invoices created or updated since last run.

Create Invoice

Action

Creates an invoice for charge-items and one-time charges.

List Invoices

Action

Retrieve a list of Invoices.

Update Invoice

Action

Updates an invoice by specified Invoice ID.

Create Invoice Charge Item

Action

Creates a charge-item attached to a pending invoice.

Get Invoice

Action

Retrieve the invoice by specified Invoice ID.

Items2

Get Item

Action

Retrieve an Item with the given ID.

List Updated Items

Action

Retrieve a list of Items created or updated since last run.

Usage4

Create Usage

Action

Creates a usage record for an item price in a subscription.

List New Usages for Subscription

Action

Retrieve a list of Usages created or updated since last run.

Get Usage

Action

Gets a usage from a subscription.

List Usages for a Subscription

Action

Lists all Usages from a subscription

Coupons2

List Coupons

Action

List all the available coupons that are created for a specific promotion or offers.

Get Coupon

Action

Retrieves a specific coupon using the coupon ID.

Plans1

Get Plan

Action

Retrieves a specific plan using the plan ID.

Credit Notes4

Get Credit Note

Action

Retrieve a Credit Note.

Create Credit Note

Action

Create a credit note.

List Updated Credit Notes

Action

Retrieve a list of Credit Notes created or updated since last run.

List Credit Notes

Action

Retrieve a list of Credit Notes.

Subscriptions4

List Updated Subscriptions

Action

Retrieve a list of Subscriptions created or updated since last run.

List Subscriptions

Action

Lists all Subscriptions

Update Subscription Items

Action

Updates the specified subscription item.

Get Subscription

Action

Retrieves a subscription.

Item Prices4

List Item Prices

Action

Returns a list of item prices.

List Updated Item Prices

Action

Retrieve a list of Item Prices created or updated since last run.

Get Item Price

Action

Retrieves a specific item price using the ID.

Update Item Price

Action

Updates an item price with the changes specified.

TECHNICAL DETAILS

Chargebee integration and API details

Review the sourced authentication and API behaviour used when configuring customer-facing Chargebee integrations in Cyclr.

API and authentication

API host
https://{site}.chargebee.com/api/v2
Authentication
API key (HTTP Basic Auth)
Credentials

Site subdomain and an API key (full-access, read-only or publishable).

Method categories

Customers, Subscriptions, Invoices, Payments, Hosted pages, Product catalog, Usage records, Events, Quotes, Orders

View vendor API documentation →

Pagination and rate limits

Pagination

Offset pagination: responses include next_offset. Default page size 10; limit up to 100. Use offset to fetch subsequent pages.

Rate limits

Limits by requests per minute and concurrent calls. Test sites default ~150 requests/min. Excess returns HTTP 429 and may lead to temporary blocking.

IMPLEMENTATION

Authentication at a glance

HTTP Basic Auth: use a site-scoped API key as the username and leave the password blank. Use separate test and live keys and keep keys secret.

Authentication method
API key (HTTP Basic Auth)
Credential required

Site subdomain and an API key (full-access, read-only or publishable).

Before you begin:

API keys are site-scoped; test and live sites use different keys; product catalog versions may vary.

View setup guide

COMMON QUESTIONS

Frequently asked questions

You can integrate subscription lifecycle, customer records, invoices, payments, hosted pages and product catalog operations. Cyclr workflows can create and update customers and subscriptions, generate invoices, record payments and respond to Chargebee events to keep systems in sync.

Chargebee uses HTTP Basic Auth with a site-scoped API key as the username and an empty password. Test and live sites use different API keys and keys should be stored securely.

Yes. Use each customer’s Chargebee site or per-customer stored credentials and Cyclr’s multi-tenant orchestration to run isolated billing workflows and map Chargebee events back to the correct tenant.

Yes. Chargebee provides an MCP server option and its API methods can be surfaced as governed tools; Cyclr can expose approved connector actions as governed MCP tools in your embedded marketplace.

KEEP EXPLORING

Related resources and connectors

Documentation

What is iPaaS?

Read more →Product

Stay in sync with Billing and Payment Integrations

Read more →Product

MCP PaaS

Read more →Related connector

Adobe Campaign

Related Customer Experience connector for customer-facing integration workflows.

Related connector

Adobe Sign

Related Customer Experience connector for customer-facing integration workflows.

Related connector

Aircall

Related Customer Experience connector for customer-facing integration workflows.

Let Cyclr handle the integrations.

You focus on building the product your customers love.

Start building for free Get a demo