Create Prepaid Usage Component
Creates a prepaid usage component definition under the specified product family. A prepaid component can then be added and “allocated” for a subscription.
Prepaid components allow customers to pre-purchase units that can be used up over time on their subscription. In a sense, they are the mirror image of metered components; while metered components charge at the end of the period for the amount of units used, prepaid components are charged for at the time of purchase, and usage is subsequently tracked against the amount purchased.
For more information, see Components Overview.
If you have the new Catalog experience enabled, taxable components must include a non-blank tax_code; sending a blank value results in a validation error.
Authorization
BasicAuth The username is a Maxio Chargify API key. The password is x.
In: header
Path Parameters
Either the product family's id or its handle prefixed with handle:
Request Body
application/json
Response Body
application/json
application/json
curl -X POST "https://example.com/product_families/string/prepaid_usage_components.json" \ -H "Content-Type: application/json" \ -d '{ "prepaid_usage_component": { "name": "Minutes", "unit_name": "minutes", "unit_price": 2, "pricing_scheme": "per_unit", "rollover_prepaid_remainder": true, "renew_prepaid_allocation": true, "expiration_interval": 15, "expiration_interval_unit": "day", "overage_pricing": { "pricing_scheme": "stairstep", "prices": [ { "starting_quantity": 1, "ending_quantity": 100, "unit_price": 3 }, { "starting_quantity": 101, "unit_price": 5 } ] } } }'{ "component": { "id": 292609, "name": "Test Prepaid Component 98505", "handle": "test-prepaid-component-9850584842", "pricing_scheme": "per_unit", "unit_name": "unit", "unit_price": "10.0", "product_family_id": 528484, "product_family_name": "Test Product Family 27791", "price_per_unit_in_cents": null, "kind": "prepaid_usage_component", "archived": false, "taxable": false, "description": "Description for: Test Prepaid Component 98505", "default_price_point_id": 2944263, "overage_prices": [ { "id": 55964, "component_id": 30427, "starting_quantity": 1, "ending_quantity": null, "unit_price": "1.0", "price_point_id": 2944756, "formatted_unit_price": "$1.00", "segment_id": null } ], "prices": [ { "id": 55963, "component_id": 30427, "starting_quantity": 1, "ending_quantity": null, "unit_price": "1.0", "price_point_id": 2944756, "formatted_unit_price": "$1.00", "segment_id": null } ], "price_point_count": 1, "price_points_url": "https://demo-3238403362.chargify.com/components/30002/price_points", "default_price_point_name": "Original", "tax_code": null, "recurring": true, "upgrade_charge": null, "downgrade_credit": null, "created_at": "2024-01-23T06:08:05-05:00", "updated_at": "2024-01-23T06:08:05-05:00", "archived_at": null, "hide_date_range_on_invoice": false, "allow_fractional_quantities": false, "use_site_exchange_rate": true, "item_category": null, "accounting_code": null }}Create On/Off Component POST
Creates an On/Off component definition under the specified product family. An On/Off component can then be added and “allocated” for a subscription. On/off components are used for any flat fee, recurring add on (think $99/month for tech support or a flat add on shipping fee). For more information on components, see our documentation [here](https://maxio.zendesk.com/hc/en-us/articles/24261141522189-Components-Overview). If you have the new [Catalog experience](https://maxio-test-wp.pages.dev/support/announcements/2026-announcements#new-catalog-experience-and-terminology) enabled, taxable components must include a non-blank `tax_code`. Sending `"tax_code": ""` returns `422`.
Create Event Based Component POST
Creates an event-based component definition under the specified product family. An event-based component can then be added and “allocated” for a subscription. Event-based components are similar to other component types, in that you define the component parameters (such as name and taxability) and the pricing. A key difference for the event-based component is that it must be attached to a metric. This is because the metric provides the component with the actual quantity used in computing what and how much will be billed each period for each subscription. So, instead of reporting usage directly for each component (as you would with metered components), the usage is derived from analysis of your events. For more information, see [Components Overview](https://maxio.zendesk.com/hc/en-us/articles/24261141522189-Components-Overview). If you have the new [Catalog experience](https://maxio-test-wp.pages.dev/support/announcements/2026-announcements#new-catalog-experience-and-terminology) enabled, taxable components must include a non-blank `tax_code`; sending a blank value results in a validation error.