Integrations / Chargebee
Chargebee
Chargebee subscription billing and revenue management platform for customers, subscriptions, and invoices.
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
In Telara
Connect in Telara
Chargebee API key over HTTP Basic Auth. Confirmed against the spec's components.securitySchemes.BasicAuth entry ({type: http, scheme: basic}) — despite Chargebee's own docs calling this an "API key", the wire auth is HTTP Basic, not a bearer/header token scheme (same shape as dropbox_sign.yaml). Use the API key as the username and leave the password blank (or any placeholder value — Chargebee ignores it, but this catalog's basic-auth matcher requires the field to be present and non-empty, so store some value). Every Chargebee account is also scoped to a "site" subdomain, e.g. https://mysite.chargebee.com — confirmed from the spec's servers[].variables.site. Store it as a `site` credential field; it is substituted into api.base_url (same {placeholder} mechanism as zendesk.yaml's {subdomain} / mailchimp.yaml's {server}). Find both under Chargebee > Settings > Configure Chargebee > API Keys, and the site name in your account URL.
In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.
- API key
- Password
- Site
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Customer | Partial — not every record the vendor holds is synced |
| Subscription | Partial — not every record the vendor holds is synced |
| Invoice | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Customer | Up to 1 hour | Removed records disappear when Telara next reconciles that resource |
| Subscription | Up to 1 hour | Removed records disappear when Telara next reconciles that resource |
| Invoice | Up to 1 hour | Removed records disappear when Telara next reconciles that resource |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: Customer, Subscription, Invoice.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty