Chargebee

This connector uses the Chargebee API v2 (apidocs.chargebee.com/docs/api).

Setup:

1. Sign in to Chargebee → Settings → API Keys → + Create a Key.
2. Pick a Full-Access key for write operations OR a Restricted Key for read-only.
3. Note your site subdomain (e.g. acme-test if your URL is acme-test.chargebee.com).
4. Set:
   • CHARGEBEE_SITE = the subdomain (without .chargebee.com)
   • CHARGEBEE_API_KEY = the full API key (live_... or test_...)

Authentication: HTTP Basic with username=API_KEY, password=empty.

Site-templated URL: https://{{CHARGEBEE_SITE}}.chargebee.com/api/v2. Test vs Live sites are different subdomains (e.g. acme-test vs acme) and have different API keys.

Amount format: monetary values are integers in MINOR units (cents) — 1000 = $10.00 USD or €10.00 EUR. Match the site's primary currency (or pass currency_code).

Idempotency: pass chargebee-idempotency-key header on writes to dedupe retries. (The adapter exposes this as a regular idempotency_key parameter on write tools.)

Form-encoded requests: Chargebee historically uses application/x-www-form-urlencoded for POST/PUT bodies (with nested keys as subscription[plan_id]=...). The adapter handles this via bodyEncoding=form-urlencoded.

Subscription lifecycle: future → in_trial → active → non_renewing → cancelled. Pause via chargebee_pause_subscription (returns paused), resume via chargebee_resume_subscription.

Webhooks out of scope.

Rate limits: 750 req per 5 min per site on Standard. On 429 honor X-Rate-Limit-Reset.

Out of scope here: hosted pages, portal session, refundable credits, gifts, transactions detail, hierarchies, comments, virtual bank accounts, gateway/payment-source CRUD.