2.6k
GitHub Stars
3
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill chargebee- _meta.json978 B
- LICENSE.txt1.0 KB
- SKILL.md8.4 KB
Overview
This skill provides a managed OAuth integration with the Chargebee API so you can manage subscriptions, customers, invoices, and hosted checkout flows through a secure gateway. It proxies requests to your Chargebee site, injects authentication, and centralizes connection management. Use it to read and modify billing data without handling OAuth tokens yourself.
How this skill works
Requests are sent to the gateway base URL with your MATON_API_KEY in the Authorization header; the gateway selects the configured Chargebee connection and forwards the request to {subdomain}.chargebee.com. You can list, create, update, and delete resources (customers, subscriptions, invoices, items, item_prices, hosted_pages, portal_sessions) using the native Chargebee API paths. For environments with multiple Chargebee accounts, include the Maton-Connection header to target a specific connection.
When to use it
- You need to list or update Chargebee customers, subscriptions, or invoices programmatically.
- You want hosted checkout creation or portal session generation without implementing OAuth flows.
- You need a centralized gateway for multiple Chargebee connections and want to avoid storing Chargebee credentials locally.
- You prefer the Chargebee API but need managed authentication and connection lifecycle via Maton.
Best practices
- Always set MATON_API_KEY as an environment variable and never embed it in source code.
- Use Maton-Connection header when operating across multiple Chargebee accounts to avoid accidental changes to the wrong tenant.
- Send POST bodies as application/x-www-form-urlencoded and use bracket notation for nested fields (e.g., customer[email]).
- Respect rate limits (10 requests/sec per account) and handle 429 responses with retries/backoff.
- When using curl with bracketed query parameters, use curl -g to disable glob parsing.
Example use cases
- List the first 10 customers to sync with an internal CRM.
- Create a subscription and generate a hosted checkout page for a new customer flow.
- Download invoice PDFs programmatically for accounting or archival.
- Create portal sessions so customers can manage billing in Chargebee’s hosted portal.
- Query subscriptions filtered by status or date for reporting and churn analysis.
FAQ
Set MATON_API_KEY and include it as Authorization: Bearer $MATON_API_KEY; OAuth is handled by the gateway.
How do I target a specific Chargebee account?
Include Maton-Connection header with the connection_id; otherwise the gateway uses the default active connection.