Subscription Billing - Maxio
API capability pack for bounded Maxio Advanced Billing REST operations. Enroll a maxio connection with base_url set to the tenant site host, for example https://acme.chargify.com for US sites or https://acme.ebilling.maxio.com for EU sites; the manifest uses https://example.chargify.com as the template host following the tenant-host pack pattern. The connection must use Maxio Basic Auth with API key as username and x as password. Reads site settings, revenue stats, MRR, customers, subscriptions, products, product families, components, subscription components, allocations, usages, invoices, credit notes, coupons, and events for billing operations, subscription support, usage billing, and revenue review. Approval-gated writes are limited to creating one customer, creating one subscription, previewing or creating one invoice, creating one usage record, creating one component allocation, applying one coupon, or removing one coupon at a time. The pack intentionally excludes arbitrary endpoint passthrough, payment profile and raw card/bank handling, refunds, external payment recording, invoice void/reopen/issue/send actions, customer/subscription/product/component/coupon deletion or archival, site clearing, webhooks, API key administration, event-based-billing bulk ingestion, subscription purge, and destructive cleanup workflows.
What this pack installs
- Maxio revenue operations digest Recipe
- Maxio customer revenue brief Recipe
- Maxio subscription revenue brief Recipe
- Create Maxio customer Recipe
- Create Maxio subscription Recipe
- Record Maxio usage Recipe
- Allocate Maxio component Recipe
- Create Maxio invoice Recipe
Show all 9
- maxio Ingredient
Trust & control
What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.